SO are you saying blocking LOLBins in Userspace would cause too many problems for home users or buisness users? Or both?
As I kind of intimated about this in a previous post, perhaps a simple (but I'm sure overly Wordy and unclear) explaination is needed:
The problem with LoLbin's is that an anti-malware application must not only be aware of What a file does but also WHY it is doing it. For instance, there is nothing wrong with a user writes a script to delete a given file, but there is an issue when a script attempts to delete many files (like for a System Wiper). In this case the security application used must differentiate between the two, flagging one (to avoid a false positive) and not the other (to catch a malicious action).
On the whole, WVSX walks this line nicely using both standard AV detection and AI functionality. However some things (like Scriptors) can get by such protection by being just a tad on the darker side of legitimate, something which I believer the brilliant folk at WV realize and so have added the FW and HIPS modules.
As a (very) simple example of the above, consider a Scriptor coded in Python (similar stuff can be done most popularly with Java or Go). One can use the "import socket" command to get Outbound access while also including a KeyboardEvent (pyhook, various commands) to monitor and package user input and then send it out to friends from the Steppes of Central Asia). This in essence will code what amounts to a LoLbin keylogger (can be prettied up to make it quite cool) and over all would not be a good thing.
If such a Scriptor was indeed coded AND was a true Zero-day, it would bypass most things (WVSX included) as these commands, both legitimate and used normally for High and Noble purposes have now in combination been perverted into creating something malicious. An anti-malware application that was not sensitive enough will allow this, while one far too sensitive will detect not only this but many, many other things resulting in a host of False Positives (and a product that detects everything really detects nothing).
WVSX seems to have been aware of this issue with the inclusion of the FW and HIPS modules as both the Network connection activity as well as the logging aspects would be blocked by changing the WV settings of FW and HIPS to the High Security level.
Of course one can also be well protected by the (cruel)CF + (default) WVSX combination.
Hope this helped...