No idea whether it's any quicker than the event stream APIs, but it sounds like the machine-readable aspect does a lot of processing that just using parsoid wouldn't get you. Parsoid is only a wikitext-to-HTML service, so you'd still need to do significant work on it to get meaning out of that HTML. The data dictionary page[1] suggests that it's exposing things like "how many citation-needed templates are in this?" (
presumably localized, since those template names change across wikis), which I could see being handy for services like that.
That said, I suspect that the real value is just the "reliable" bit on that summary page.
> Written agreements, no additional content restrictions, SLAs, 24/7 support, and contractual guarantees against surprise breaking changes make working with Wikimedia Enterprise safe and reliable at scale.
i.e. If I was building a big enterprise thing using wikipedia data, getting a SLA and a promise that us rando open source devs won't completely change the APIs on a whim would be nice.
[1]: https://enterprise.wikimedia.com/docs/data-dictionary/