RDM Database replication question

Currently I've set up RDM to connect to a central MSSQL Database which contains all the session entries and structure for administrating our servers/resources in all locations worldwide. RDM and this database is used by our Server Operations team which has members all over the world.
Turns out that the closer a team members is located to the database, running the RDM on his client machine/management server, the better the performance.
While within Europe the performance is acceptable, in Asia and Americas it's not. Hence team members are reluctant to use RDM and the benefits of a globally unified administrative structure.

After talking to one of our database guys, two possible options came up to mitigate the weak performance in Asia/Americas.

1. Replicate Database to Asia/Americas
- We expect mostly read traffic, so replication traffic could be neglected
- Problem: Unclear which tables to replicate, is there any recommendation/experience from Devolutions regarding RDM SQL DB replication?

2. Place regularly updated read only copies of the Database in Asia/Americas
- Not very comfortable for the users, but easy to implement
- Changes can only be performed on the Europe DB, e.g. Updating personal credentials, personal session entries. Small drawback for the users
- Question: Can RDM operate with read only access to the Database?

While the structure for "All Items" is administrated only by myself, other team members can and should administrate their Private Vault, storing credentials and personal sessions entries there, associating their individual credentials with folder/session entries in the "All Items" section.

Could you please answer the questions in the 2 proposed options and maybe provide me with a best practice approach on how to handle such a scenario?

Kind regards
Holger