There are potentially several things blocking it from working

• Blazor uses their own runtime initialization path and the crypto initialization call is not included in that path (or public)
  • [blazor][wasm] load .js and .wasm assets by runtime aspnetcore#43049
  • [wasm] asset loading for workers #73484
• Blazor's publish targets limit what files end up in the publish output history
  • [Blazor] Update SDK to account for the crypto worker file sdk#26966
  • [wasm] rewrite crypto-worker to typescript #73073
• For Blazor WebAssembly (hosted), consider enabling cross-origin isolation by default aspnetcore#42114
• Provide a way to disable using subtle crypto on WebAssembly for the .NET crypto APIs #73386
• [wasm] crypto deadlock fix #73537
• [wasm] fix error cases in assets loading #73702