Don’t worry I’m fine, I’m not claiming you’re intentionally spreading misinformation either, and I’m sorry if I lead you to believe the contrary. Like you said these are development and technical low level issues which are complex enough on their own. As a matter of fact, just by using the SDK as-is, without any hack, you can distribute add-ons which are injecting foreign code into the FS2020 process and/or granting access to call any DLL on your system… both from WASM and JS/HTML layers. And I won’t even try to explain other types of WASM sandbox evading in exploiting your CPU flaws similarly as with the Spectre exploits, because I think this is off-topic enough already, but you can search my post history for more details.
What I’m advocating consists in implementing in the SDK direct access to what the SDK is otherwise using indirectly. These are technologies/APIs which would be protected the same, by the Windows Kernel, as they are already protected the same when used indirectly via the current SDK… In doing so, the SDK would be offering support for a larger category of add-ons needs, and it would support more effective implementation of the most complex airliner gauges as well, like the ones found in PMDG, FSLabs, Tolis, and many other similar aircraft.
Therefore the only reason to me this is not implemented has nothing to do with security (it is no less secure) nor with technology (they are already using this technology indirectly via the SDK). And this has nothing to do with the Xbox either, because the PC version is already offering a certain number of PC specific capabilities like the user-level access to the Community folder, and there is no particular reasons to not offering PC specific SDK additions either.
And just to make it clear: this has nothing to do with Reality XP “wanting” to load external DLLs… we wouldn’t need to with the aforementioned SDK addition… which again raises the question: who benefits the most from lecturing me…