I agree with what [I think ...] Mike Rowe is saying: the two concepts can be used together, and they very often are.
For instance, when we say that *"you are essentially breaking the work down into Epics, (etc.) ..." well, there's that same phrase again, just in different context. We've still got work, and we're still breaking it down. (But the scope-and-boundaries, and goals, of our breakdown efforts are now different ... and perhaps, "multiple and parallel.")
In the context of these projects, I still find value in applying WBS concepts at two distinct levels:
At the initial stages of the project, as we are trying to develop, or at least to predict or prognosticate, an over-arching expectation for it. But we then allow the team's self-directed activities to discover the details while the project is periodically held up against this initial breakdown (and, the breakdown is revised).
On a micro scale, awareness of WBS principles can prove to be more effective in ordering the team's short-term next activities, than "simple consensus" might be.
WBS concepts are also extremely valuable in determining what the initial project breakdown ought to be, in a large effort that might involve multiple [scrum/agile/what-have-you] teams. In my opinion, it's extremely important that each team be set with well-thought-out scope and boundaries, and that anticipated interactions between the various "team boxes" are as well-understood as they reasonably can be at this point. (And that we then revisit it from time to time, and publish new revisions.)
"Traditional [waterfall] WBS" broke down, so to speak, because we can't predict the entire future before we begin. Iterative methodologies (scrum, agile, and so on) were developed as a response to this, realizing that "well, we don't have to." But I'd argue that they certainly didn't discard any of WBS's good ideas. They just started applying them at different times, at different levels, and with both short-term and long-term objectives. By doing this, we think that we've improved the bathwater, but we didn't throw out the baby in the process.