I made a suggestion around the lines of this a while back, but this would be problematic in data accessed by multiple servers. If server A is out of requests and updates key 1 to “q”, server B still sees key 1 as what it was previously. DataStores really aren’t capable of using the same key across multiple servers for games with large amounts of servers, but in rare occurrences, keys may need to be accessed across servers on a scale that doesn’t break them (for instance, making a purchase on an auction item).
The majority of the use DataStore sees, at least in my experience, involves data only needed in the current server, but DataStores still need to be able to support correct syncing across multiple servers. I believe the best way to do this is to leave the current xAsync methods, but add Get, Update, and Set without the Async prefix, exhibiting the behavior you described.