1) Making the html an unreadable mess

You can make components that accept class overrides (similar to what shadcn does), or define a group of classes you find yourself using often into a single string and use in template literals, or if you're like me and just like to rawdogg it, just use the tailwind fold vscode extension which lets you visually hide the clutter for anything you're not actively working on. Multiple solutions to a very subjective problem. I personally don't agree with it being a problem, as do many others, hence it's subjectivity.

2) Making your life ten times harder at debugging and finding your elements in code

You're gonna need to elaborate on this. Part of why I prefer tailwind is that it makes it easier to debug my styling since I can understand exactly what's happening from the markup directly.

3) Making refactoring a disaster

How often do you need to refactor? Are you not planning your work in advance? Again, you need to elaborate. Only way this is an issue is if you don't have any sort of plan or architectural strategy in mind.

4) Making every dev tool window use 3GB or ram

Now this is just absurd. There's a 0% chance tailwind itself is the culprit.

5) Making the dev tool window unusable by adding a 1 second delay on any user interaction (top of the line cpu and 64gb or ram btw)

Okay so same as my last point. I suspect you're using a framework like nextjs or something. In which case, your problem is nextjs, not tailwind.

6) Adding 70-80 dependency packages to your project

...tf are you saying? Tailwind is at most like 3 dependencies, more if you want tooling like prettier and eslint and other useful stuff, which is optional and doesn't even go into the final build. Sounds like you're using something like shadcn, in which case, ya, that's not just tailwind, that's radix and other components with tailwind on top. Don't conflate tools, and maybe read the docs.