Hard to fix class-naming mistakes

Not sure if this is more a bug report or feature request (or note to future self).

If I accidentally give 2 migration classes the same name and then try to fix it later, I get reports of
"No migration class WhateverMigration found" and "No class currently exists for the following migrations". I try various combinations of clearing cache, unregistering orphans, and (re)registering classes, and even a drush registry rebuild, but the errors keep popping up.

I managed to do it by editing the migrate_status table to give the migration the new class name, followed by clearing cache, followed by migrate (re)register.