But also many (lazy) Android-developers do not just care if their app go to Stopped-state. They just assume a user would always run their app in the foreground and then quit it when a user is done with it. It then gets frustrating if a user goes back to the app and expects it to be in the same state where (s)he left it.
Lets not go to too deep in this OT, but the terminal window program's backend could (should) be programmed to be Service and IntentService and it could do just that what you describe. Terminal's GUI would be a normal Activity which connects to that backend which is running CLI processes and bash. The GUI part could be killed in between when a user leaves it (the terminal window) to the background.