Yep, hopefully my abuse of notation didn’t confuse anyone. The issue is that the dll being generated is the WASM runtime with the WASM bytecode being compiled into native code within. The WASM part is contained in a sandbox by the runtime and is highly limited with respect to what it can do. At runtime MSFS loads each WASM dll and pushes in a handful of function addresses. Those functions are the only external things that can be called from within WASM.
OTOH, a standard Win32 dll has full access to the operating system APIs as well as any other code that they might choose to take advantage of. In case it hasn’t been clear, I’m arguing that developers should have the option of developing add-ons using a standard Win32 dll (as they do on all of the other major platforms).