Yes. I have had those rules with OSArmor by the side.
However if you've disabled process execution from the wscripts and cscripts and disabled script execution itself, there's no need for these rules. You might not have the ntvdm.exe in your system. It's an old component that allows 16-bit applications on 32-bit Windows, as well as the execution of 16-bit and 32-bit DOS applications. You can disable execution of 16-bit NTVDM processes in OSArmor.
And if the script interpreters are executed from non-standard locations, OSArmor blocks them under "Suspicious Processes".
Still if you wish to set those HIPS rules, 'block a process' in either app only.
ESET's list is quite small and standard though. For RW protection, you can also refer to their
FW recommendations if you haven't tried yet. SysHardener also has a good general list of processes to block in FW.
W.r.t. learning mode, make sure to not indulge into any risky or suspicious activity for the time being. And do it on a system you consider clean.