Hayes, below is a brief summery of how you could do this in PAT.
Below is a screenshot of PAT with an OpenStudio measure and two EnergyPlus measures. Among other things, the first measure associates an epw file with model. In this use case it is only useful for the epw, because the changes made in the actual model will be overwritten by the next measure. This isn't published yet but I can email a copy to you.
The next screenshot shows a measure I made as a proof of concept that lets you inject geometry from an OSM file into an external IDF file. The external IDF file is then fed into the run workflow in place of the IDF generated by OpenStudio. If you don't check the box to use the OSM geometry, then the result is passing the entire un-touched external IDF into the workflow. This measure is on BCL
If your locations are different enough then you probably want to make a simple EnergyPlus measure to update your design day information, maybe along with water main and ground temps. Or if you have changed these elsewhere, you can make design alternatives where you pair the correct IDF up with correct epw. I showed the PV measure in the workflow just an example. You could replace this measure with one that alters site information stored within the IDF file.
This same workflow would work fine on the Analysis Framework spreadsheet, but with that or even with EC2 in PAT you do need to make some minor alterations. The measures are pointing to local files on my computer. When the measures run on the cloud, it won't see those files. The best way to solve that would be to create a "resources" folder within the measure for any files you might refer to. If the files are within the measure they would go up to the severs and would be available when the measures are run. The Xcel EDA Tarrif measure demonstrates this.
@HayesZirnhelt. You may want to tag this question with things like 'energyplus', 'parametrics', and 'mac ' or 'mac os' so that folks who subscribe to these tags (i.e., mark them as interesting) are notified.