You cannot really maintain that. The controller has to adapt. That is what the two reset signals are for. The synchronous one can be trigger by application logic (for example some sort of timer) to re-calibrate the touch controller.

Intentional user input has fairly consistent characteristics, as do each of a variety of noise/drift/interference sources. The key is to safely and accurately recognize/estimate each of those to remove or report them. I suspect now people would prefer to use some form of machine learning, but realistically there are fairly low expected power requirements, which make that difficult. There's also a battle between low latency stateless techniques and more stateful techniques that require rapid recovery when they get something wrong.