CL options are typically arguments passed to the script. It is not itself, another script or command. If I'm not mistaken, you have to have the ExecutionPolicy set before you're able to run a PS script. The rare times I've done this, I used a batch script to set the ExecutionPolicy, then use that same batch script to run the PS script, then disable the ExecutionPolicy again. You might be able to just set your ExecutionPolicy via GPO and leave it enabled but I'm not sure what the risk is with that.
That's pretty much what I've been doing - setting the execution policy and then executing the powershell script from a batch file.
It works, but I'd much rather be able to run the powershell directly if possible!
I'd put in a feature request for LANrev to set the execution policy before trying to run any PS scripts via LANrev. Instead of having to have it set ahead of time.
I like that and added the feature request