At the moment, is_deeply from Test::More is all that I need to get the job done, so I intend to make a 'base' that requires just that (not counting YAML::Any).
I agree, that I can (and probably will) use Test::Deep to support more advanced comparison methods. Yet, I see this as an optional expansion, using both: Test::Deep and mine 'base', maybe as separate (sub)package.
I have looked into the source of Test::Regression and I can not just use it's (only?) function as-is. I would have to rewrite it to do what I intend, in the way I intend... or write another, similar sub... and add some post-exit handling to the module... I'm afraid, that after all the refactoring, not much would be left from the original module. :( Not to mention, that in my case, workflow is a bit different.
I can't tell, whether it's actually good, or bad, as I lack the experience, but for the moment it does not 'feel' right to me.
I hope, that when I post the working module for review/critic this will be more evident.