There is always a schema.
True, json has no formal explicit schema attached to the data.
However, there is still the ad-hoc informal schema that's defined by what the code interacting with the data does. Because this tends to be poorly specified and hard to get at, it's rather annoying to work with.
JSON is inherently "schema-less". So this provides us with no grievance.
> something that has, at best, extremely weak types
You provide the reader with nothing that indicates that strong-typing is important for JSON use-cases.
> schema equivalents that are bolted on, rarely used, and end up relying on humans understanding exactly what the data looks like
There are no schemas in JSON.