I agree neither of those seem like good reasons to pick tailwind.

My take is that it removes needless indirection in any codebase that already has “components” - react/vue/solid/etc, template partials, functions that return html strings, whatever. See comment here: https://news.ycombinator.com/item?id=42804831

For that reason, plus it’s concision, I find it more productive use of time compared to css-in-separate-file.

If you don’t have components for separating semantics from presentation, then tailwind is less a good fit.