This is probably not very easy to do. While I do like to find families of related keysets, the truth is that most devices have fairly unique (and incompatible) infrared control systems. And this is a good thing! When you've got a room filled with audio and video devices, you don't want the controller for one accidentally triggering another. So, there are dozens of different control protocols, and even in each protocol, there are unique "device ids" that are supposed to keep remote controls from triggering the wrong device. It's generally only when manufacturers get lazy that you can combine device keysets. (The exception here would be Sony -- they've done an amazing job of making sure that their IR remote controls are all backwards compatible, forwards compatible, and yet still avoid interference between one another. I've gotta take my hat off to them.)

However, there is another possibility; if you could determine both the IR protocol and the device id value used for a given device, you could then run through all the possible command values. Most protocols only have 128 or 256 possible commands. This still seems like a lot of work to me, but I think it might be doable...

My hope is that, for the majority of cases, if there's an unsupported device that has a compatible keyset in Pierogi, it is because both device manufacturers are simply using the same IR hardware (and repackaging/rebranding it). And so, they should have identical keysets. In this case, Pierogi's current "Automated Keyset Search" should be enough to find the compatible keyset...