The thing is that it appears to be extraordinarily hard to do Agile right. I think that any system that is so difficult to implement correctly is an inherently flawed system.
Interestingly, in many ways they also weren't all that different from what Agile is intending to bring. They still involved something analogous to "sprints", they still allowed for course correction and pivoting during development, and all of that.
Agile seems to position itself as the opposite of "waterfall", but outside of large corporate environments, I'd never seen a shop that actually used waterfall as described by the Agile community.
There's only two valuable ideas in agile, that are actually broadly applicable.
1. Do continuous integration.
2. If it doesn't make sense to do something, don't do it.
You don't need to get into philosophical discussions over the manifesto, and the purity of your adherence to agile philosophies, or any of that nonsense.
What you do need to do is to go and deploy Jenkins (Or whatever the new hotness is in the CI world), and don't build features that nobody needs.
I think we should stop referring to those things as "Capital 'A' Agile" ( which isn't even an actual thing to begin with) and refer to them by their actual name: Scrum, Scrumban, SAFE, XP, Crystal, RUP, USDP, AUP, etc. At least we can try to make the point more clear that when we criticize these things, we're criticizing a specific "thing" and not some catch-all term. Given that there is no concrete methodology named "Agile" to actually criticize.
It really depends on the customer if that process is something that can't be influenced. Although of course we're as an external party often have more freedom in that regard than a customers direct employees.
EDIT: added some specific questions
FTFY