This is all about what tools enable.
This issue is critically important to people who have a much higher privacy need than the average person. Consider an abusive ex tracking down their victim in an unknown new city.
If the profile is indexable, the abuser is trying to either use OKCupid's search (which returns results with a high degree of randomness), or using things like "site:okcupid.com $interest1 $interest2", which is noisy, to say the least. This task looks hopeless quickly.
But if someone provides a database of profiles, the job gets much more tractable. Suddenly, you've enabled the attacker to filter by people who have 1,2,n interests of their ex, search with photographs of their ex, hell, even use facial recognition. Some of these things were kind of possible before, but with a database they are likely. If someone builds a "find your ex" web frontend on this database that uses facial recognition technology, it becomes accessible to everyone, and maybe even popular.
Saying that this lesson should be educational is theoretically nice, but doesn't match how users interact with products in the real world. Anyone who has worked on a product with millions of users knows that the average user (a) doesn't know that there are settings (b) they don't know which things are controlled by settings (c) they don't know how to find the settings, and (d) they don't know how to change them. This is so common that I no longer believe that users are responsible for the implications of default settings (and OKCupid's defaults are, inconveniently enough, Public).
Tools usually are capable of both good and bad things, but a database of profiles has limited upside, and a huge downside. Like, this thing had better be curing a minor fatal disease for the amount of trouble that it will cause.
To take an analogy: if a child plays with matches, you teach the child not to do that, explain how fire is dangerous, etc. You don't light a fire and hold the child's face down on it to burn them and make the lesson "painful". Yet when it comes to deliberately making sensitive/intimate data about people public that basically is what you're advocating for: the potential emotional harm that can be done to the people involved is off the charts.
* Requires effort to access
* Is in out-of-the-way places many people don't know about
* Is in a form that's difficult to consume
Even though it's "public", in many ways it behaves as if it isn't, since until one of those conditions is removed people don't really bother to access it, pay attention to it, or try to consume it.
In other words, it's one of those "if a tree falls in the forest and nobody's around to hear it" situations.
So information which is only available to someone with an account, but on a system which grants accounts for free to anyone who wants one, typically is thus seen as "private" or at least in a "not really public" state until such time as someone massively aggregates it and makes it available to people without accounts, as happened with OKCupid.
Another issue has to do with the expected lifetime of the information. Users on OKCupid expect that when they remove their accounts the information is no longer available to anyone.