Kosta, your theory is wrong as it doesn't take into account any of the information provided by everyone.
This problem has persisted FAR longer than a couple weeks. The 12.0.3 Switch firmware update came long after this problem first started showing up. Of course, that's evident to anyone who views the history of this bug and earlier comments that can be easily viewed above. I've been experiencing it for months, and some have reported it persisting for over a year.
Switch firmware updates have had nothing to do with improving or worsening the current incarnation of this bug, which appears to be linked directly to a user's save file data becoming unstable after enough hours of playtime.
No improvement with the 1.17 update.
Also can confirm that 45% is the main hanging spot, but it's probably irrelevant to the issue itself. It takes a long time to clear the black screen just to get to the Mojang loading screen. In total, after starting the game on Switch, it takes at least 15 minutes to get to the main title screen to play the game. Then, depending on how big the world is you're trying to load, it could be another 3-6 minutes. So you're looking at an average of 20 minutes just to START playing Minecraft, and you better pray it doesn't crash once you start.
If you want to play a little Minecraft on your Switch on a bus or a train, forget about it. Want to play at home? Load well ahead of time, and if you need to take a brief break, put the Switch to sleep with the game running to avoid the long startup again. It's unacceptable by modern standards and still pretty bad even by old-timey "reticulating splines" standards.
So if you only have an hour to play, about 30% of that hour will be spent just starting the game. Smh.
Same problem, ridiculously long startup time for a profile with a lot of playtime. Tried numerous solutions without any improvement. Restarting/shutting down Switch does not improve load times, as it did for users experiencing this problem last year. Starting in airplane mode also doesn't help at all (previously users reported this worked and it was thought to have been related to the system making cloud save backups).
Deleting multiple worlds/resource packs, etc., also does nothing to improve loading on the affected profile. Only completely deleting the save data for the profile fixes the problem, which mean the player loses all progress. And for what? It seems highly likely that if the player plays long enough, the same thing will happen again.
We really need more information from the devs about what the problem is and what's being done to solve it. Should we bother deleting the affected save data, or wait for a solution? Is this something completely beyond our control or can it be prevented? Will affected save data load normally once the problem is addressed, or is it permanent? Knowing things like this will help players decide if it's worth it to endure the extremely long startup time in hopes of saving the worlds they've put so much time into, or if they're better off starting anew, or if they should just stop playing altogether.
Saw Gavin's comment, tried playing on my main account and I'll be damned, it's true. Can confirm, my corrupted save data now loads normally. My condolences to those who deleted their save data to fix this problem.