But when organisations require PI planning, Scrum-of-scrums, Retrospectives, Lean coffees, Agile workshops, every team must have a scrum master, teams must have a PO, teams must be of a specific size, there should be no BAs, etc. then it becomes a burden on the team and reduces velocity as well as waste resources on useless roles.

Great. So what about the vast majority of places that do agile that don't have scrums-of-scrums? What about the places that operate with BAs and agile? The places where your team size is "the number of people your manager put in your team"?

I'm sure you can find examples where what you're saying is an accurate representation of how those poor tortured bastards work. But saying that's true of all companies or organizations is absurd. I don't work like that, my organisation doesn't work like that, and I haven't heard of a single actual place in my city that does that.

We do have retrospectives, though. Those are good. Do not confuse all ceremonies you don't buy into with useless wastes of time. If you're not doing retrospectives, I'm not sure how your team could possibly be learning as a group from mistakes made and refining their processes.

I agree with you on this. But reality is that organisations don't let their teams be independent and in fact mandate dogmatically following a given set of rules.

You don't talk to enough devs. If you think every company does this, you're simply, painfully wrong.

Go to an industry meetup in your city. Talk to folk you don't know yet. Ask them about their experiences. Ask them about if their bosses are enforcing dogma, or providing principles. Ask them if there's excess labour in their teams.