There are a lot of trees added to OSM in European countries for example, not everyone needs to know that e.g. Berlin has tree data in this DB and Frankfurt in another one.
The interest in such data is going to tend to be local or be forced to take into account the nature of the data collection (and thus benefit from directly accessing the curated source data). An example of the latter would be an academic analysis; to pull data from OSM, it would need to start by determining geographic areas with good coverage, or the results would be utterly meaningless.
Namely, changes to open records laws to make it okay to work on data sets that are not strictly public domain.
Here's an example. The National Park Service can't treat OSM as their canonical data store:
https://www.nps.gov/npmap/blog/nps-plus-osm-equals-places-of...
People play blame-the-ODBL, but there's not really any epically strong arguments against adjusting the public records laws to be a little more flexible.
It's anyway kind of pointless to jam such data into OSM. Most rendering tools are happy to use multiple data sources, so someone interested in such specialized information can just get it from New York City.
That doesn't mean that it absolutely shouldn't be added to OSM, but there should be some clear motivations and benefits, not just helping (hypothetical) lazy people (that might be interested in the data) avoid a JOIN (which is hyperbole, for this data you don't even have to match anything up, just use it together with a base map).