How about I use one of your examples.
> It's fine to think of `f a b c` in Haskell as being equivalent to `f(a, b, c)` in Python, even though we know that, under the hood, f isn't really a function of 3 arguments.
All abstractions leak. The fact that Haskell is always curried means that you always have to be aware of currying.
There are many kinds of problem solving. One is "how do I solve {x} using {y} in some clever way." Haskell is great for those folk. Another is "How do I solve {x}."
Here's one way to distinguish these two groups. The first sends "look at my cute solution to {x}" to their friends while the latter say they send "look at what I built".
To put it another way, when a user community is dominated by folks who write papers/essays about the tools, you've got a tool for folks who want to play with tools.
Haskell is wonderful for a subset of those folks who care a lot about tools, specifically those folks who think that mathematical purity is important.
There are other goals.