I wouldn't recommend using this in two senses:1- It's against the ToS obviously. The analogy I've used in the past that seemed to catch on is that it's like going to an all you can eat buffet, bringing your whole extended family and trying to pay once.
2- Legals and ethics aside, don't build products that competitively rely on this, the moment they patch it you will be out of business, it's like making a business out of blackhat SEO during the Google era. At least if you are going to do it, cash out quick, you are in the rug pull space.
Have some sense and taste, we are professionals here, if in your pesonal life you share your netflix account, bypass DRM, throw cigarrette butts on the floor, cut in line or use handicapped spot without being handicapped, that's one thing, we all do something marginally wrong every once in a while. But on a professional setting, these go from being normal personality traits to being red flags that will silently leave you marginalized from serious software.
I'm extrapolating here, but it's a pattern I see very often in other areas where it's even wronger. For example lots of people use unofficial APIs instead of using Meta APIs, they connect to WhatsApp unofficially (See OpenClaw crowd), instead of following the procedures in place to reduce spam (and let Meta monetize of course). Even worse is people that want to scrape Facebook, sure it's a pain, but most the API stringency comes from the Cambridge Analytica scandal, if you do this shit and you then complain about Meta you are being hypocritical, can't have it both ways.
I know we are in hacker news, but there's a lot of nuance. Running youtube-dl to download some cat videos isn't the same as hosting youtube-dl as an API and charging 5$/mo or building a business on top of it.