Interesting perspective, but to me it seems to conflate the process part of Agile methodologies with the requirements. In other words, requirements that explicitly INCLUDE scenarios other than the "happy path" (example and template at https://cygnustechnologyservices.com/services/services-more-effective-user-stories/) and that evolve as a result of team participation rather than being "handed down from on high" (discussed in more detail at https://medium.com/@frickingruvin/the-greatest-user-story-ever-told-f72643919ade) have solved most of these problems in my experience.

The biggest problem I have found with Agile methodologies is the belief that high-quality and consistent technical design (what most people call "architecture", discussed more at https://medium.com/@frickingruvin/defining-architecture-edcb334d5cbb) and implementation will result from an inherently distributed and uncoordinated system in the hands of "leadership" that consistently prioritizes delivery speed of quality.