Yes they should be.
Depending on your build/deployment setup you may find that replacement variables enable you to have fewer patches and to differentiate between environments. Alternatively you can have patches for each environment and remove when packaging up artifacts before deployment.
The same would hold true for configuration transforms. The build ...
SCWPD are just zip files, so you can extract and modify them to add you adaptation.
In essence, the biggest differences for your topology are in the web.config.
Especialy in the appSettings part where the role is defined (role:define). In theory you can just reuse the XP1 package and than go into it and change the web.config.
Or you could also just use ...
I had used a console app which allowed me to change the file name. Below is the code snippet of the console app
public static void UpdateConfigs()
var filesWithPath = DirSearch(@"C:\path\to\app config folder\Include");
string configNames = File.ReadAllLines(@"C:\Users\username\Desktop\Enable Configs.txt");
var counter = 0;