Performance issues running VBScript code because of calls to th Antimalware Scan Interface (AMSI)

I am working with an application that processes a table and for each row it is creating a very simply visual basic script and executing it before other processes are executed. The Vbs script is just an If - Else statement with some simple logic that returns true or false.

It turns out that the application process time has doubled when moving from Windows Server 2012 to Windows Server 2016 because of the AMSI checks done on Windows 2016 but not on Windows 2012 by Windows Defender.

Is there some way to reduce this impact without having to disable the AMSI checks in the server?

One thing I would like to know is if the AMSI calls are done when the script is created? Maybe there is the optoin to create the script as a function and register it so thatthe AMSI check needs to be called only when the function is registered. I do not know if this is possible since I have not been able to find much information about when Windows Defender calls this interface.

I want to remark that the use of VBscripts is something already implemented and changing it is not seen as an option.

Thank you, Sergio