Given the additional information I would agree that Module::Pluggable would be a viable way to go. You can scan in the plugins you have and build a hash of the kinds of file you can handle (with module names as values) and then call as needed for each file type as you encounter them. Each module could have a standard method that would "register" itself in the hash that could be called as part of the M::P search/init routine.

That is basically what I did for my primary use case. I had to take in various CSV and XML files and call the correct module to transform them into my internal format for further processing.