Blazor WASM runs in a sandbox and has no access to client filesystem, dom, network, etc. It uses js interop for this. So there is nothing a Blazor WASM can do without js that Blazor server can not do. That is Blazor WASM is purely computational except for javascript message support.
so even if you configured your Blazor server site to load a WASM, you would need javascript to call the WASM code, and the WASM code would need to call javascript to do the operation you wanted to do in the first place.
note: not sure why you would call javascript for encryption for server side communication. this seems a security flaw.