It's a cool idea, however maintaining such list is going to be headache. For example we might change provider or add new provider in the pool that is not (yet) blocked. So the endpoint that was blocked might be available again or the company unblocks the IP.
Also some companies simply block access from any non-residential IP's all together, so it won't really matter which VPN you are using, if all of the IP's belong to data center.
Thank you!
I've noticed that switching to WARP Cloudflare often solves this problem. Interestingly, this is currently the only way to play Rainbow Six Siege in Russia. The game doesn't allow logins either directly or via Xeovo VPN, throwing an error in both cases. The only exceptions are WARP(wg or awg1.5) or ExitLag and similar services that market themselves as "traffic accelerators", but are essentially VPNs (I'm surprised that some kind of exception was made for them, but not for Xeovo, which looks more like a personal preference of the company). Interestingly, even modifying packets using projects like zapret (tpws and nfqws), which typically restores access to blocked resources locally, ultimately fails to fully resolve the problem of connecting to Raibow Six Siege servers specifically in the Russian region, making the use of a VPN a necessary measure. A common combination is the simultaneous use of zapret and warp (launch sequentially to access warp), which also only complicates life, as well as errors or problems launching some software in the presence or detection of the windivert driver, turning all this, even in such trivial things as video games, into an attempt not only to bypass the provider's dpi, the state gfw, but also corporate blocking systems of companies (Ubisoft) that deny service under far-fetched pretexts.
In general, this topic is more for informational purposes, to monitor the situation in order to understand where and how things are going.