I'm afraid that if such a module was to be general enough it would be either just as low level or way too complex.

For the time being try to forget about the modules that might be available and take a few of those tasks and try to express their differences in a way that would be detailed enough for a computer (using a hypothetic module). Try to express as a config file or as function/method calls of a module the slices and the filtering and the mapping ... you may easily find out that what you end up is too complex and that there really isn't a way around using your preferred XML parser and DBIx module directly. Or maybe you find out that what YOU need can be built on top of that selected parser and DBIx easily with the exact bits that can be controlled that you need.

In either case I don't think you can get away with something like a shared script and a bunch of config files. I'd expect more luck with a library that implements the common bits used by a new script for each import.