on first look I would say that HIPS self defension feature triggers when something from Scriptlogic is being executed by Explorer.exe. I would follow Scriptlogic's policies - I gathered this might be a Windows policy management-type software - whether such a policy enforcement or rigths control might interfere with HIPS. On the other hand I would also check if HIPS has an exclusion feature for this type of rule. Althoguh it seems that HISP is only seeing explorer.exe not more which suggests that the offending code is either in a program run by startup or in the registry under HKLM\Microsoft\Windows\CurrentVersion\Explorer\ShellExecuteHooks, which is also a frequented place for other code to load when explorer.exe loads.
Maybe scriptlogic has a module that you might not need (very often) which could be removed or disabled from loading from places like above.
Hope I could give an idea.
Ordinarily I'd say that perhaps this was an example to create an exception. However, I'd really suggest not doing that since a) it involves self-protection of Host IPS itself and b) Windows Explorer is the (shill) trigger. If it wasn't self-protection I'd be more inclined to say "exception" or if you could explicitly identify the known scriptlogic processes involved.
I highly suspect there's a driver conflict here since remote tools like this often times employ add-on video drivers or drivers that look at the video subsystems.
This is a case where you definitely want to open a support ticket. Perhaps there's something on the Host IPS side that can be done.