The real issue is that iOS is not respecting the users choice to disable motion, and in cases where a user suffers from a motion intolerance, it's absurd they have no way to disable motion to meet their needs.
It's software... I'm pretty sure what's happening is a new feature gets built, with animation, and the team responsible forgets that there's a "reduce animation" setting that they should take into account.
I have an iOS app that has a disable animations setting and I frequently forget it exists. My app is a few million less lines of code and a couple thousand less engineers than iOS.