Page load speeds by themselves can be painful. Open devtools and have your browser throttle to poor 3g speeds.
Try browsing around. even well optimized sites.
Now try uploading a couple dozen files through an api.
This is legit what some users deal with. In New York state even, you don't need to go that far to find poor connectivity.
Even if all your users have awesome home connections, think sales people taveling to a client. or on site inspections of a manufacturer in a warehouse that's mostly metal and has bad wifi.
I thought you were giving an example of how bad connections can get, and saying that the extra latency would make it worse, but in that situation it's a drop in the bucket.
200ms latency isn't that bad, but I'm seeing more 800-2000ms latencies with some users depending on physical location. at some point latency kills usability. Especially when trying to get through a complicated QA or inventory process.
Because this implies that.