Users don't care about the app architecture. They just want an app that is stable and doesn't crash.
If there was an API that allowed an app to restart itself from scratch, then inexperienced developers would abuse this functionality to get out of a problem whenever any kind of an error occurred, instead of learning how to properly construct their app or to fix the underlying bugs causing the errors.
This would lead to a bad experience for users, because there would then be many apps that restart themselves whenever they run into trouble.
Therefore, it is very unlikely that API authors for any platform would be willing to implement an API like this in an imperative UI programming environment.
If you are having issues with state, state restoration, and state merging, then the best option for you is to research ways to mitigate these issues that have been studied in theoretical computer science and software engineering for decades.
Users may not care directly about the architecture of an app, but they do care about the quality, and the quality is directly determined by the architecture. An app that bails out and restarts whenever it runs into trouble is not well architected and is not a quality app.