Yes, I often hear that Scrum is a framework; and then I hear from the same people that "they did not do it right", or "they did not follow the Scrum Guide".

They can't have it both ways. If it is a framework, then one can deviate from it, add to it, etc.

About the Scrum values, I would question why we need them: they are so abstract - "courage"? Really. What does that even mean?

I think that the Scrum Guide was nothing more than an attempt to monetize Agile. The Agile Manifesto has a set of values - we don't also need the Scrum values.

Things have also changed. Most digital products today are not single-team products. Scrum is not a good fit. Scrum is a single-team process. I know that people have layered things on top of it, like LeSS, but Scrum is just not a good fit - neither is XP. The things we build have changed. Scrum is very incompatible with Behavior-Driven Development. Scrum puts too much focus on the team, instead of the product and the end-to-end ecosystem. Scrum's ceremonies distract teams (and product groups) from things that really matter - there is so much more to building a product today than one's standup and the Scrum ceremonies and roles - so, so much more. Scrum masters don't learn about those things because they are obsessed with Scrum. They live in a bubble. If they were to talk to programmers at large, they would hear how dissatisfied programmers are with "Agile" as they have experienced it - which is usually Scrum.