Sort of, but it still ends up with a hard coded path.
The install/update script I have seen (and cannot remember what now), simply wrote the required text to a new file (having checked and deleted any existing file) direct to the required systemd folder (/lib/systemd/system) - no symlink required. Any paths can then be generated in the script before writing the text.
No views.
If you remember the Pauls (@pb66 @Paul) had a discussion suggesting a data structure that accounted for multiple installations. This seemed to only cover the data though not the other bits.