Trellix ePolicy Orchestrator freezing PowerShell Desired State Configuration

Question

I've been dealing with Powershell DSC freezing for several months after the required deployment of the noted ePolicy orchestrator. Typically doing things like killing all instances of powershell wmi commands and powershell.exe backdrop processes, then forcefully killing the dsc document in all states may let a run slip by, but it takes a long time. My traffic is encrypted and due to these challenges I only do manual pushes. My DSC code does have some imperative code so at some point I'm looking to reduce pssessions in case rapid calls are problematic, but if anyone out there is versed and has experienced similar issues, I'd love any tips.