I'm sure this attitude is behind the 90% useless "security reports" that they receive.
That said, an issue like the one reported is inarguably on the wrong side of that boundary, both conceptually (not requiring host key verification by default) or empirically (by the data collected by the reporter).
Thanks, though, for your unnecessary, gratuitous, and frankly absurd editorialization.
API design is critically important to security whether or not you believe it to be — we've learned this the hard way through decades of treating keys and IVs as "stringly typed", as overwhelming numbers of developers use `rand` to generate keys and use hardcoded IVs. An API design that encourages misuse will be misused, and the onus to improve the default situation should be on the author of such APIs.
The latter are worse in my opinion, because they're harder to fix.