K.
So the Switch is apparently the headquarters of FBI (pun intended), which is impossible to break into without any sort of proper authorization.
Got it, I'll just keep begging Daddy Nintendo along with the millions of others so they can release features already present on the 3DS in 5 years, and do it in a half-assed way.
The main problems on the switch are those:
* it's a rewrite from the 3ds os, with lessons learned with the 3ds applied.
* the aslr makes game exploits everywhere, where we don't have some type of scripting or jit so hard, that it's nearly impossible in most scenarios to pull it off concistenly. But the browser could probably still work as entry point.
* it's a micro kernel architecture, so everything is split into parts with as little permissions as possible, so you would need to move from the entry point, so the game, webrowser, hid systemmodule and so on to higher permission modules/kernel/trustzone with more exploits.
* the privileged parts like the kernel are very small compared to something like Linux. So it's relatively easy to have a full understanding of the code and its interactions. If you are interested in checking it out yourself, you can beginn with checking out atmospheres exosphere (trust zone) and mesosphere(kernel) source code, because those two are the parts you need to exploit to get deep enough into the system for cfw
* for hardware glitching you need high enough control over the cpu power, by reducing the power very low in a specific timing for the cpu to glitch out and get the wrong result for an operation(in the modchips case it's the comparison of the public key part hash to the one in the fuses of the cpu, if I understand the attack correctly). This attack also needs some trigger to make it consistent, since there are some timing randomisations in the bootrom, which is the nand read in case of the current modchip.
This means it's not something you can do with something like the joycon rails.