Yep always switch the logfile after completing a hot backup
i.e. when tablespaces (and their datafiles) are backed up. Switch the logfile. Then backup the archive log files.
Hint: You can always past a unarchived redo log as an archive log, in the event a recovery complains the database or more specifically datafile is out of sync. Just don't reset logs before you do this
I would suggest (if you have the benefit of time) to always run a job to check for table corruptions. In these days of NOLOGGING, nasty things can happen.
It is one of those things which should be a grantable privilege (Are you listening out there ORACLE?) not a right, as people can get carried away and then complain when their table can't be recovered
Performance... Push the envelope!