Maarten - you have great insights on so many things, but I am going to have to respectfully push back somewhat on this :-)

I think the problem is not so much in what Scrum says, but the fact that it is so prescriptive - and that prescriptiveness is not Agile.

Also, while Scrum is claimed to be a framework, it is rigidly defined, and the Scrum Alliance does not allow anyyhing to be taught that is not precisely defined by Scrum.

And Scrum defines a lot of things that are really distractions. Scrum Masters tend to focus on Scrum ceremonies - "enforcing" Scrum. But teams only have so much capacity for discussion and reflection, and that capacity gets sapped away by discussion of Scrum related issues, when it would be best focused on CI/CD issues.

Finally, Scrum is focused on a single team, but unless one is building something trivial, most issues are about what happens between teams, and in support of teams.

Scrum also defines very simpleminded models for complex issues. I have written about how they keep changing their mind on what a Scrum Master is supposed to do - and that is the key "leadership" role. In fact, they are confused about leadership in general.

So yes, Agile is reflected in some of Scrum's prescriptions, but that does not make Scrum Agile.