We are aware of the aswAMSI.dll-related entries. This is a bug on Microsoft side; we're reported this long time ago - but nothing is happening.
Technically, Avast is correctly registered as an AMSI (antimalware) provider. Some time ago, Defender started using JavaScript engine - which also attempts to load the current AMSI provider. However, due to the settings in the Defender process itself, it doesn't "like" the module signed with an Avast (i.e. non-Microsoft) signature. So... it's up to Microsoft to decide whether they want to actually use AMSI in their JavaScript engine (or rather in the engine used by Defender), and if they do, to accept further signatures, or provide another way to allow that DLL in their process.