it's a good question and understandable use-case Joseph. There is only one idiomatic (not necessarily convenient) way to achieve this which I know of which is Format identification by Extension will return that generic PDF for you to associate your command with. This might be more useful with separate pipelines/workflows that promote FPR level distinctions. i.e. to make up for the inability to modify FPR on the fly.
This impacts format identification globally however so you wouldn't have a PUID against those files in future. Similarly, there is a way to achieve something like this customizing Siegfired/Roy but not without this impact too.
From a dev perspective, you could write a Django database migration to write the data needed for this many-to-many situation. I'd be interested to know if anyone has explored this on the list, but I don't know of any and haven't done it myself. In a different context, we've used a database injection to disable rules such as FITS. I could imagine a generic pattern that could be used for other FPR like input/modifications.
Maybe there's some food for thought there? Either way, hope you find a good balance for your use-case and I'll be interested to hear how it goes and what others say.
Best,
Ross