I concur with Ulf, trying to work around Android's life cycle to avoid a crash is the wrong way to go about it. If possible, it will take a lot of effort and will produce an app that doesn't perform the way it is expected (people generally expect to be able to use an app, switch to the phone or read a text message, then back again and continue where they left off). You should rather figure out what is causing the crash and fix that.
Sounds a lot like the "back button" fiasco in web applications. People have problems in their app when the back button is used, so rather than fix the bugs, they try to disable the back button. Wrong approach.
Do you have a really good reason (a good reason) for trying to buck the system?