Summary
We've discovered what Scrummerfall is, why it happens, and how it sets an organization back by ascribing all the negative outcomes of traditional waterfall development to Agile development. This outcome is acceptable to the Hubricist; whether an individual or a corporate culture, opposing Agile allows for moving forward in a comfortable, yet competitively damaging manner.
My suggestion for stopping this dynamic is for Agilists to have the courage to call out Scrummerfall, even when it's uncomfortable to do so. We don't have to be the "word police" all the time, but anyone who is interested in the success of an organization shouldn't allow the term Agile to be used to describe projects where that description just doesn't fit.