The Group Policy template is located on domain controllers in Sysvol, and is used for the storage of the Group Policy object(s). A typical Group Policy template folder might look like this example:
systemroot\Sysvol\SYSVOL\Streetmarket.com\Policies\ {34975054-fd77-df75-54fe-074936850457}
The Group Policy template folder contains subfolders, including, but not limited to, the following:
adm: Contains all the .adm files for this Group Policy template.
Scripts: Contains all the scripts and related files for this Group Policy template.
User: Includes a Registry.pol file that contains the registry settings that are to be applied to users. When a user logs on to a computer, this Registry.pol file is downloaded and applied to the HKEY_CURRENT_USER portion of the registry. The User folder contains an Applications subfolder.
User\Applications: Contains the .aas files (application advertisement scripts) that are used by the operating system-based installation service. These files are applied to users.
Machine: Includes a Registry.pol file that contains the registry settings that are to be applied to computers. When a computer initializes, this Registry.pol file is downloaded and applied to the HKEY_LOCAL_MACHINE portion of the registry. The Machine folder contains an Applications subfolder.
Machine\Applications: Contains the .aas files that are used by the operating system-based installation service. These files are applied to computers.
If you understand how these files are applied and what they do, it is possible to do something like what you want, but you would be much better off just reconfiguring the policies on the second domain.