By also commenting out UNDO_MANAGEMENT=AUTO I managed to get the DB to start with NO undo_tablespace specified and management set to MANUAL.

However I can still not DROP the offline old UNDO tablespace because of this active rolback segment. The alert log continues to have entries when SMON is attempting to recover these segments. The logs are growing extremely quickly and other alert logs for individial processes are clogging up the folders.