Without trying to solution, I could envision a way to provide GS a view into the .sfdx/someorg/sourcePathInfos.json Granted, this file isn't under source control, but could be moved to a special location so not to disrupt DX and support GS. This file contains all the file locations and may be able to help GS with a source to org deployment. The inverse, pull new org to source, may require a default drop folder and then the dev can refactor/move to preferred location.
Jeff
Without trying to solution, I could envision a way to provide GS a view into the .sfdx/someorg/sourcePathInfos.json Granted, this file isn't under source control, but could be moved to a special location so not to disrupt DX and support GS. This file contains all the file locations and may be able to help GS with a source to org deployment. The inverse, pull new org to source, may require a default drop folder and then the dev can refactor/move to preferred location.