The Xbox is a closed system - even the developers have no way to inspect the files system on it, and instead use an emulator.
But there is now a clear pattern here - and after 9 months on Xbox and MSFS, I think YOUR post here is the most significant in terms of identifying the underlying problem:
There is a lack of proper error trapping, examination, handling and messaging - AND there is data corruption still happening.
For me this started with SU9 rendering MSFS unplayable on Xbox, and then Jorg Neumann (in a Dev Q&A video) talked about bringing in the best coders from Microsoft to solve the issues - which added up to “memory oversubscription” and “cache corruption”, among a list of other things. I do acknowledge they made huge improvements to stability - which shows they can do it. But it required outside help - and I think the code culture needs fixing. Error trapping and examination needs vast improvement.
My experience has been that on Xbox (a closed system) with only MSFS, when things start to behave badly and others don’t seem to have the issue, I uninstall, factory reset, reinstall - and the problem tends to go away. And if it doesn’t, then I am confident in reporting a bug. But it clearly demonstrates that data corruption is STILL a huge issue. Just today 2 others on this forum (PC users) posted that MSFS had corrupted their Windows User accounts - and Microsoft’s own support told them they had to wipe them out and start over! That’s incredibly bad code!