I've never built or worked on a service where the JSON payloads were so large that (de)serialization accounted for a significant portion of the timing profile

I'm sure lots of them exist, but for your typical CRUD API, this has not been a phenomena I've run into.

I suspect the vast majority of services are not dealing with such massive JSON documents that doing serde on them becomes a material part of their latency breakdown.