no man, you got me wrong, that not how i intended to sound, I am also a professional dotnet developer, 7 years, not as tenured as you. I was just pointing out that that the standard dot net library will not provide you that much benefit, if you port it to wasm to use in javascript, not just will you face the interoperability cost, you will also not get much from most of the dotnet standard classes that deal with low level os calls, File system. Since c3 is run from a browser, you will hit the browsers sandboxed limitation, and even using 3rd party library (any unity api is out of the question since those are compiled to mono), but you will also have compile those down to wen assembly.
on that note, one of the guys who use to work at microsoft started working WebWindow (https://blog.stevensanderson.com/2019/11/18/2019-11-18-webwindow-a-cross-platform-webview-for-dotnet-core/) which if it gets mature could be of interest to wrap construct3 games.