[Bug]: Metamask needs to function without wasm

### Describe the bug

launched via:
chromium --js-flags="--jitless --wasm-jitless"

metamask loads in browser but is not functional. wasm memory is not secure & many major websites allow arbitrary wasm deployments by partners

### Expected behavior

metamask should function normally in a browser without wasm support

### Screenshots/Recordings

_No response_

### Steps to reproduce

launch chromium via:
chromium --js-flags="--jitless --wasm-jitless"

### Error messages or log output

```shell

```

### Detection stage

In production (default)

### Version

13.7.0

### Build type

None

### Browser

Chrome

### Operating system

Linux

### Hardware wallet

_No response_

### Additional context

_No response_

### Severity

in my opinion severe, this is a show stopper

Start by reproducing the production build in Chrome with `--js-flags="--jitless --wasm-jitless"` on Linux, then trace where MetaMask depends on WebAssembly during startup and normal use. Done means the extension remains functional in that environment without weakening its expected security behavior; the issue does not name a file or test to target.

Written by the indexing model from the issue text.