JVM yes was initially designed for Java alone, but its research successor, GraalVM, does understand LLVM bitcode thanks to Sulong.
As for "superior" WebAssembly sandboxing, it doesn't protect against internal corruption, due to lack of bounds checking on memory access. Which allows for injected scripts to try to coerce a loaded module to change its behavior. No need to escape the sandbox, sometimes changing the outputs is all that an attack requires.
It remains to be seen how many WebAssembly CVEs will appear when it starts to be more widely targeted by black hats.
And if those WASI modules happen to be written in languages like C and C++, I expect a couple of them to show up.
The existing model does not prevent exploits taking advantage of internal memory corruption inside the sandbox.
[1] https://words.steveklabnik.com/is-webassembly-the-return-of-...