dbi VS Payload_Launcher

I would also reccomend you get dbi responder as your first app. It's MTP Responder option will let you access the switch from your PC which makes installing stuff later much easier. https://github.com/rashevskyv/dbi/blob/main/README_ENG.md I would link to the download page but it's in Russian.

Download the latest dbi.config and DBI.nro files.

You can use DBI for Force language per game.

Go to the latest DBI release.

It's here! https://github.com/rashevskyv/dbi/releases

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.