Webhooks were initially brought out to eliminate a lot of the polling that needs to be done on the API. And since EventSub is the latest incarnation of the webhook system, it is left to believe that much of the same mentality applies.
And working with over 1,350 individual broadcasters (approximate number being tracked as of this posting) just feels like an absolute terrible workaround for data that is not utilized by my service.
All in all, this change just feels like it was developed without taking into consideration larger scale project use-cases that don’t require scoped data and it will make it difficult in the future to continue to scale as needed. Granted, I already have an elevated quota for EventSub, but I now worry about what will happen when I get closer to hitting that hard cap. Will I have to introduce fluff features that are likely to not be used by a large enough customer-base to justify the development time just to save on a few dozen subscriptions in my limit? Will I have to beg and plead for a limit increase like I already have to do with YouTube?