List migrations separately but use single migration class
It sounds like you're trying to force a tool to do something it's not supposed to do. The migration tools drush migrate-status command only provides a high-level overview of the migration batch work associated with a migration (current state, migration source entities found, number of entities, migrated, etc.)

There is drush migrate-messages if you're wanting to inspect individual migrations that may have failed. But if you're wanting a super-granular, per-entity, view of each migration item then you're probably looking at building your own tool or debugging a migration as it's being processed.