Has there ever been a problem where the original full backup seed becomes corrupt causing any future volume restores to have a problem?
Have not seen any issues related to backup file corruption since VEB was released. Just in case something happens with the backup chain – the new full backup will be created during the next job run.
Should I move the backup set to an archive folder and erase the destination of the backups to occasionally to force a new full backup to be created?
The default backup mode is forever incremental so no periodic full backups are supported. However, you can use a standalone full backup (not affected by retention settings) or change the backup destination in backup job settings if you want to start a new backup chain from scratch.