In my experience, Solution Manager uses the predefined [**Stored Procedures**](https://community.denodo.com/docs/html/browse/7.0/vdp/vql/stored_procedures/predefined_stored_procedures/predefined_stored_procedures) provided by Virtual DataPort like GET_VIEWS, GET_VIEW_COLUMNS and DESC VQL commands in a complex combination to reproduce the metadata of the Virtual DataPort Server's metadata as VQL fragments and executes the VQL thus formed in target environment. This can be easily traced by enabling [Denodo Monitor](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/monitoring_the_virtual_dataport_server/denodo_monitor/denodo_monitor) and checking the queries executed.
As for the Version Control is concerned, with respect to the [**Solution Manager**](https://community.denodo.com/docs/html/browse/7.0/solution_manager/administration/configuration/vcs_configuration/vcs_configuration), it is only used to be a **"Backup"** to protect the environment by creating a VQL for the entire target environment and rolling back to it if the Deployment fails.
Also, it is not allowed or permitted by any external tools (including Denodo Tools) to access the metadata directly, but through the Virtual DataPort Server and all the interaction between the Virtual DataPort is always through VQL which is very expressive and "safe" to transfer between systems.
Hope this helps!