I understand, but I think the discussion got off track by the "touch animation" phrase. That means something different to many of us. The Touch animation mentioned earlier that is available in SE applications simply turns any object into a button. Using touch animation I can import a graphic object and apply touch animation to it so the user can touch it and take an action, just like they would a push button object. It has nothing to do with giving you feedback that the button has been pressed.
As you know, indicator tags control the appearance of a button based on the state of the referenced tag instead of "am I pressing the button or not". I have never liked indicator tags for the exact reason you mention. When someone presses a button, they expect some sort of feedback to the button press. And I completely agree with that. There should be some feedback to show the button press was detected by the system, otherwise they smash the button over and over. It's like a button for a crosswalk. Some have a light that turns on when you press the button. Others don't, and people just repeatedly mash the button never getting any feedback.
So yeah, it was the phrase "touch animation" that raised questions. You meant something different than what some of us thought you meant.
OG