The latency would be incurred several times when loading a single wall. As an experiment, take a moderately complex web app and deploy it in a different continent from the database it connects to.
If you're at the point of storing data on different continents and being aware where it is stored, I'm not sure what is stopping you from batching your trans-continent queries so that you only hit the trans-continent latency once.
