
You mount databases against a Web Application, not site collection. If the Site Collection in 2016 is at "/", what you would want to do in 2016 is backup and restore the site collection to a new content database in the desired path (i.e. /sites/site2). When that is done, mount that new database on 2019.
This ensures the path is what you want it, and by using Backup-SPSite/Restore-SPSite, it generates a new Site ID which are unique per-farm.