Eh, that's honestly not a great solution. It's a bandaid workaround. Getting better detection on when to auto-save or auto-saving at known good times is a lot better. The multiple auto-save solution is a good fallback but not the definitive answer. You could also just make the player invincible for 1-2 seconds after a save load and then also cast their position to the navmesh to make sure you save them in a place that they aren't going to immediately fall to their death or out of the map. A lot of open-world games now just restart your character entirely leaning up against a building in the world or camping or whatever. Making it feel like the player character has their own agency and actions while you just play them for a while.

It's also a compounding issue, that's just one of the technical issues over many. In the end, it really depends on the type of game you are building. Every game is released incomplete, even the biggest masterpiece, the developers wanted to do something more. So you balance the technical issues between saving the real-time states or just saving off some simple data like you were at this mission in this area, with this inventory, with these player stats. Even that is a lot to keep track of and test. To then add stuff like AI states, active combat, randomization data, etc. I understand why a lot of roguelikes don't save most of the active game data. After all, developing games is very hard and the save system is not a high priority to the general experience of the game.