I have no intention to try that commercial software (which said free to try without detail on the condition or expiry info).
In any case, if you have it "compile" to exe, say abc.exe, from the script named abc.vbs, I would suggest you try to change the query string from the above to this for testing.
[tt]
squery="select commandline from win32_process " & _
"where (not ((commandline like ""%command.com%"") or (commandline like ""%cmd.exe%""))) and " & _
"(commandline like [blue]""%" & replace(wscript.scriptname,".vbs",".exe") & "%""[/blue])"
[/tt]
(of couse you can fabricate case to break the simple use of replace like calling the vbs abc.exe.vbs of similar names, but that is just a guard, very artificial name. Just try to avoid those as a scripter has control on the name of the script name.)
From a broader point of view, I would suggest the vbs should not just be a wrapper spawning other process (vbs... or exe, com) to do some job. In that case, the application abc.exe would surround the control after spawning those processes and diminishing largely the usefulness of checking of the sort.