The default policy covers the most commonly encountered stuff.
How paranoid are you ? Or, how paranoid of a configuration do you want ? How much do you want to block ?
Block *bitsadmin* if you are worried about malicious shortcut (*.lnk) files. It's deprecated, but it is still on your system. Malicious shortcuts can also call interpreters. Block hh.exe because of .chm files, but a malicious .chm will usually just call wscript or cscript to download other malicious files from the internet so you're already covered with the C:\*script.exe policy. We can sit here and make a long list of potentially abused file types. The vast majority of stuff is blocked by disabling interpreters and the user space policies. For a second opinion on this general concept you can ask
@Andy Ful.
My best advice, the best course of action is to install AppGuard and soon after just bite the bullet and configure it hard-core one time. What you're doing, really, is protecting against cmd.exe and many exploits. Beyond this initial configuration it is just maintenance and disable stuff temporarily when you need it. Then backup the xml. Ask
@Umbra.
After you get that worked out - instead of fiddling around with security softs, their bugs and the problems they cause on your system, you can focus on learning about malware. You focus on security knowledge instead of the damn tools to protect your system.
Whatever you do, you should use what you like and stick with it.