> There is little point in using WebAssembly if you control both sides of a boundary

Mozilla is using this to secure native dependencies: the WASM boundary ensures the memory and function access is correct.

https://hacks.mozilla.org/2020/02/securing-firefox-with-weba...

> The core implementation idea behind wasm sandboxing is that you can compile C/C++ into wasm code, and then you can compile that wasm code into native code for the machine your program actually runs on.