No one is asking you to do that. Run Roon as yourself, and let Roon write to your own home directory. On Mac, we write a tiny lockfile to your home dir, and then write quite a bit to ~/Library/Roon/. Users running the app should have permissions to write to their own directory. This is pretty common UNIX behavior. You are failing because you can’t write to your own home dir.
chmod u+rwx $HOME; chown `whoami` $HOME
Roon is meant to run locally per user, and not system wide. If you want to force Roon into system wide install, you might be able to succeed with looser permissions, but I wouldn’t recommend it.
If you install Roon into a shared location and run as a different user than who owns the file, you will break self-updating, but nothing else. Also, our dev team is split about 50/50 on Mac vs Windows.
That’s why we write to your user’s home directory, and not to some global directory.
All licensing is done based on your Roon account + machine identity, and nothing to do with software install.