Yes, but do a copy action not a move action, to ensure the destination folder's security settings are applied to the files. The DBA team I am part of has been relying on the method I described for two years of DR exercises and it has always worked. Our daily backup generates fresh copies of the System Database files every day (as soon as the backups are created, we via restore each to a different db name and file location then detach the new db).

For a recovery, we no longer restore the System Dbs from backups - we just copy the most recent copies of the files back into the original location(s) and then start up the engine. The only catch we have encountered is that you have to take ownership of the detached files and grant yourself access to them before you can copy them (upon detach, SQL Server reduces the rights to the MDF and LDF files so that only the identify that detached them has any access).

😎