Curious as to what the JS bridge overhead is like for both latency and throughput. What would the performance look like if you tried to serialize DOM updates over the bridge and replay them on the JavaScript side so that you could build DOM UIs? Have you measured # of updates per ~16ms?
(I know there is some proposal that might allow WASM to interact with the DOM directly too, but I don't know how likely it will be merged.)