Not any time soon.

WASM was adopted as a minimum viable product in June 2015, 3 years later there is still a lot to be done.

Currently the only information that can pass from one context to the other is a number. That means if we want to pass anything else to/from wasm and js we need to come up with some kind of system to get around this limitation. Currently the approach is to put the the value into shared memory and then return the address in memory where it can be found, but then you need a way of getting the length of the thing you put there.... oof, this is already complicated.

While there may be an opportunity to move past these current limitations, it is going to take a long time to get there. Currently the Webassembly Roadmap is almost all about stabilization and infrastructure and while the post-mvp features are listed as "in-progress" none of those are directly about DOM interaction. Also "in-progress"is a reference to the state of the proposal, not the implementation that means the proposal would need to be completed, then accepted and then browser developers could start to implement them. Needless to say WASM is a long way from being a JS killer.