Maybe your business logic is in the wrong place. What if you used a service to handle your business logic and made your templates depend on that. Then your service could run any time something changes and you could use observables to update dependent views.

I have been exploring lots of different ways to manage state recently and there are places for setter/getter pattern and ngOnChanges. I think people need to spend more time thinking about how state affects their components.