LOL. I’m saying it’s useful but not necessary with containment setup with @cruelsister 's configuration but as long as you know enough to interpret the HIPS alerts then great. CS’s setup is very much a set and forget as anything unknown will be sandboxed any changes etc are done in containment and cleared simply by clicking on Reset Container.
I’ve been trying to figure out a workaround and a cause of your constant TaskManager blocks but CIS will protect itself and log any intrustions even from safe apps. You can beef up the HIPS by some advice I had from @DecimaTech some time ago but that only really makes sense if your reducing the protection from Containment.
HIPS Advice:
“under protected files adding ?:* will cause HIPS to protect all files on all volumes and drives. For protected registry keys while not necessary, unless you want greater coverage, you can add *\Software* and \System*. Under protected COM interfaces, adding \RPC Control\ntsvcs monitors access to the service control manager, LocalSecurityAuthority. allows you to control process token privileges, and {} and . will cover many COM interfaces by CLSID and ProgID.”
Or you could even see if @jay2007tech is still around. He’s done some historical posts about fuly tweaking out CIS in his topic here: https://forums.comodo.com/t/whats-your-method-for-locking-down-cis/321331
Just a thought but you could run a 3rd party virus scan like Norton Power Eraser just for a second opinion to confirm your system is safe but CIS won’t let you get infected unless you ignore the alerts.