This would only be relevant if you had a direct fibre link in a straight line from your house to the service. It's packet switching\routing etc. that introduce latency. And even if you DID have direct fibre, the worst case scenario for distance - server on the other side of the world, but with no other latency accounted for - is about 200ms, even half of which would be noticeable in many games.
I'm not saying it's impossible to do game streaming, but you can't just divide the distance by the speed of light and say it's low. That's not really the issue.
Only when network is underutilized, and there is no throttling/bufferbloat.
In practice, it’s a lot worse than 200ms. 500-700ms are typical for servers on the other side of the planet.
Average Pings from Digital Ocean regions: BLR1: 251ms FRA1: 129ms SGP1: 206ms
Other sites: yahoo.co.jp: 179ms rakuten.co.jp: 138ms belarus.by: 167ms
As most things go, YMMV.
The problem with latency is that it adds up, lag from the server, lag from the TV, lag from my brain, lag to my fingers, lag from the controller to the machine, lag back to the server, lag in processing and then start again.
Client-Server lag might be acceptable in isolation but not as part of a system.
So not really anyone. And that's in an extremely latency friendly environment where the servers are just up the road.
The bigger limiting factor I think will be bandwidth, especially in America with the awful internet provider situation.