Consider this scenario: you have a couple of Pro templates saved in Portal, that you're workgroup uses, and these templates, for the sake of this example, deal with emergency services: connections to EMS, Fire, LE, FEMA, DHS, NIFC, etc...type enterprise geodatabases and gis servers. Since you were "Born Ready", you think ahead and you've download these templates to your hard drive because you know you're going to be in an ICP somewhere in a cold parking lot with a 500k Verizon Mifi and no way to connect to your Portal, but being "Born Ready" means you can double-click on these template files while you're chipping the ice out of your coffee at 6 AM and fire up a Pro Project that has all of the connections you need.
WAAAAAAIIIIIIIITTTTTTTTT FOR IT!
Not so fast...imagine your surprise when you Pro Project opens, and you go to look for that FEMA GIS server connection in "GIS Servers"....not there. What!?!?!? All the folder connections you defined in the template are there...but not the GIS Server or Enterprise DB connections.
Even though you're working a Zombie Apocalypse Response, the next 16 hours of your day does not have to be as dystopian as the grocery store running out of milk and bread or as upsetting as Carl getting bitten. You can open a local template that honors GIS and DB connections by copying it to C:\Program Files\ArcGIS\Pro\Resources\ProjectTemplates, or, in the "New" Project UI, browse to the location of the downloaded template. Not as fast and cheeky as double-clicking on the template, but, as a disaster junkie and someone who binge watches Walking Dead, you're used to things not working, Pelican Cases with broken latches, and being surprised.
Take home message here: The open project from template behavior needs to be consistent and honor GIS Server and DB Connections regardless of how the template is accessed. Every second counts.