I am also a SONAR refugee, and not having track templates looked like a deal breaker for me. However, to get SONAR Track Template functionality within the PreSonus One Console/Mix View at least, as @edgarstephens suggested, I've done the following as a temporary workaround:
Let's assume that "Song_A" has a track "TrkTemplate" with some desired settings and routing
1. Open Song_A.
2. If TrkTemplate outputs to a Bus which contains an FX chain you want to retain with the template, you will have to create an active send to that Bus on TrkTemplate and resave Song_A.before moving to the next step. This redundant send will then preserve the Bus routing in any subsequent import.
3. Open a new song (let's call it "Templates")
4. Click on Song > Import Song Data (or Ctrl+Shift+I), select Song_A and import TrkTemplate with all the console options checked
5. Rename TrkTemplate to the desired name for that instrument+routing in Templates for later reference
6. Save Templates
Now, every time you want a track template complete with Bus routing, track names and sends, you can access the template by importing song data from 'Templates'. It's not 'right-click' close, but close enough to be bearable, and the Templates file itself doesn't have to be loaded up in order perform the import, so theoretically should be able to contain as many pseudo- Sonar Track Templates as you wish!
I've tested this with a 16 mono channel out instance of Native Instruments Battery with several inserts and sends on each channel all routed to a single stereo Bus with its own insert FX. I've also tested it with a folder-packed Drums setup - 5 mono and two stereo channels - with FX and Bus, and it retains the folder, names and routing. The key is the redundant Bus send in step 2.
PS: Remember to switch off the redundant active send created in Step 2 in Song_A and resave Song_A.