Payload_Launcher VS NX-Update-Checker

For updating Atmosphere itself, I recommend installing the Payload Launcher homebrew so you can get back to Hekate. From there, you can use Hekate's USB feature.

Payload Launcher - hijacks Atmosphere's "reboot to payload" function to launch user-defined payloads

Payload Launcher This is effectively a non-Tesla-based way to switch between payloads. Probably not super useful if you're going to lean into Tesla.

If you never shut the Switch all the way off, then you don't 100% require the jig; you can reboot between payloads using the Payload Launcher homebrew.

You can in fact do so with the Payload Launcher homebrew, actually.

Payload Launcher to simplify moving from one environment to another

You can use the Payload Launcher to reboot to a given payload file directly from Atmosphere. Additionally, Atmosphere allows you to name a payload file reboot_payload.bin and reboot to it from the Switch's menu.

Then you can grab the Payload Launcher homebrew to get around the fact that you can't use Hekate to swap between sysNAND and emuNAND.

Alternately, you can use this tool to do it.

There's almost* nothing wrong with the Switch modding scene on 15.0.1, save for a couple very minor edge cases that in the scheme of things are nothingburgers (coming to mind most readily is the fact that NX-Update-Checker will crash if you run it while docked unless you have the log flag set. Why? Nobody knows.).

NX-Update-Checker - a handy utility for checking which installed games need updates

NX-Update-Checker This allows you to quickly check which of your installed games have available updates, as opposed to needing to go through them one-by-one.

Yes, actually! No Tinfoil required: https://github.com/16BitWonder/NX-Update-Checker

The NX-Update-Checker homebrew is exactly what you need.

NX Update Checker to very quickly scan for game updates so I don't have to hunt through each of my games