Assuming you're currently not working with Scrum (or other agile frameworks) at the moment, why would you care about ScrumButs? I mean, different companies will have different "maturity levels" on Scrum (some with more buts, some with less).
Scrum is a tool with a purpose, not purpose in itself. If you join a company that's not yet mature enough (or with some ScrumButs) you can look at it as an opportunity to understand how Scrum could help the project to address the problem. Maybe Scrum isn't the answer; maybe the people who say they're doing Scrum are not quite sure 'what does that mean', either.
With that said, you can identify some teams that are "moving towards" agile methodologies when they fall into any of the below characteristics:
- Very hierarchical teams, not allowing courage to flourish
- No focus on incremental deliverable with business value at the end of an iteration
- Different specific roles within the team for analysis, development, testing
- Only development team doing Scrum
- Hard requirements / deadlines being imposed on the development teams
As a side note, worth to notice that some companies and projects are still learning the difference between "being agile" and "doing scrum" and using both expressions indiscriminately, but that could also be considered a smell per se.