Avast is detecting the signatures stored in memory by agent.exe, but only when the process is running. When the actual executable on disk is scanned, there are no detections made, and the file looks clean. Avast does not kill the process as a result, but issues alerts to 200 some pieces of malicious code found inside the process.
It is common practice for antimalware tools to encrypt their signatures and temporary files. For example, Malwarebytes Anti-Malware encrypts it's quarantined files so that other Anti-Viruses like avast don't detect these quarantined files and remove them.
This is most likely part of the reason why Immunet itself has exclusions for various temporary file folders for various antiviruses including Kaspersky, Avira, and Avast.
Thank you for your understanding in this matter, I am glad to see this sort of support.
I would also like to mention that Avast does not appear to make these detections unless the user specifically initiates a scan involving memory. This would include the default settings for a full scan, and is also a selectable option for custom scan settings.
This being the case, one would consider it a minor incompatibility but it may also cause issues with other AVs that scan memory; I'm sure you already know this.
Thanks again for the support!