It's just not how regular people think about manipulating information - in the real world, sorting a set of any interesting size is impractical if not painful. You can literally ask a loaded question - "is there any way you could sort those to make XYZ easier?" and folks will avoid that in favor of other method.
We saw less than 10% of users ever employing the sort controls; that's not zero, but it's low enough that you can't depend on them to cover use cases.
The problem with your examples are that you're not really showing "sorts" from a user standpoint. What a user is really doing is effectively filtering for the "show me the N least difficult", not "sort by difficulty, ascending." Also, sorting on a relatively scaled value make more sense, but a lot of the time the values in a column don't have that kind of relationship. What's the "least zip code" good for?
Developers love to put in sort controls because they cover lots of use cases and don't take a lot of thought to implement. And mentally, they tend to think about sorting a lot anyway. But my experience with looking at data from non-developer users has always been that they rarely use sort options when available (and search filters, either, btw. ) You see about 5% of users employing those controls.
So the developers think they've solved certain use cases by providing sorting, and users don't see those cases as covered, because they don't see that they can use sort to solve them. It's better to just not put in sort, reduce complexity and find other ways to cover those cases that users are more likely to employ.