Your post didn't say anything about corruption. That could be caused, among other things, by design issues or accessing the be on a cloud drive or user actions, such as killing Access from Task Manager while it's trying to do its thing. A VPN will slow you down so that will be a factor as long as it is in play. Question is, if that is the way it must be then all you can do is concentrate on the other potential db design issues assuming you must stay in Access. The only other option I know of is to use a web based database, and that you can no longer do with Access (AFAIK). This whole area of remote access isn't my expertise, which is why I stated that unless you are quite knowledgeable in Access design principles, you might want to either read up on the basics or have someone look at yours if you must stick with your current architecture.
I note that the link didn't provide any info on Citrix, just Terminal Services. My experience with TS is in a corporate setting where users had no pc, just a keyboard and something that looked like an android box. The statements made at the other forum wrt TS reflect what I know of it, but I can't tell if the writer was referring to anyone having TS at home. That's out of the realm of my experience. The TS I used was part of a wired LAN - it's just that most users didn't have a pc. If I had to access TS from home, I still had to use Citrix, so that's the breadth of my experience with those.
It would have been interesting to know what the writer had in mind with replication. Access hasn't supported replication since I think version 2010. He must have been on about a roll-your-own version, which I would avoid unless you have experience or access to such experience. There was a reason why replication was dumped, so I'm afraid I don't see the point in recreating that horse and buggy.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.