Still disagree, and I think you're thinking of really obnoxious examples. I'm imagining about a ~150ms animation for the following:
1. A sidebar sliding out from the side
2. Dialogs swooping in and out from the top of the screen
3. Form panes sliding out when replaced
These quick, almost-no-time visual cues are incredibly important at giving your interface a sense of presence and physicality. Without them, your UI elements are flickering in and out of existence without any perceivable reason, and can often leave the user wondering what changed.
“Why did this get so slow?” Is a real and common complaint with such changes and why OS’s allow people do disable so many animations.
Check out these demos: https://material.io/design/motion/speed.html
Example: you can't effectively convey a menu becoming a button without an animation. Without an animation, the menu disappears and a button appears, but there's no reason to believe that they're related. A 100ms tween from one to the other is all you need. Our brains are very good at relating motion, not objects blinking in and out of existence.
Remember, those 100ms delay gaining information which also delays every action that happens after them. So, the cost is real.
Worse, people can break 200 actions per minute for well known systems. Which makes this far worse as it’s slowing people down more as they try and get more done.
It’s the same issue as flat buttons, users need to know what’s clickable, and what has been clicked. They don’t need shading etc, but feedback has masssive utility. Sadly, our field generally lacks the kind of real feedback that corrects such incompetence.