Elaborate. I figured it would be easy to do this with just 8 pins, if you just make sure each controller sent/received non-similar signals through different pins and just made the ground and vcc the same pins (1 & 8) for all cables.
PSX uses 7 wires. 360/PS3/xbox/PC uses 4 (you could even use a button select for the USB connection so that you can tell the board which system it’s plugged into). Gamecube uses 3. Dreamcast uses 5 (4 if you don’t need to hook up the sense line in the cable). Saturn uses 8.
Even if you decided to go all out like Toodles’ UPCB and start adding in older system support:
SNES uses 5. Genesis uses 9, but not many people are clamoring to use sticks on the genesis. The only people you’d get for the SNES would be people that played TMNT:TF and KI on there, basically. N64 uses 3 wires. NES (God forbid) uses 5.
This is all pulled from the hex files in the UPCB source. One of the main reasons the UPCB is unaccessible is that to make a cable, you have to solder wire from different pins of the UPCB to the Ground and VCC pins on the DB15 to tie those pins as low and high respectively, then solder in the signal lines. A lot of work for just a cable. The reason the MC Cthulhu has taken precedence over the UPCB is the ease of making cables. You can either have tentacles worth of cables hanging out of the case, each soldered to a different row of the Cthulhu, or you can solder an ethernet cable to the 1st row of the Cthulhu’s pins, feed it into a Neutrik RJ-45 jack, then crimp cables into the corresponding pins needed to get them to the rows they need to be in. The Cthulhu knows what system cable is plugged in by what wires are connected and where.
I won’t claim to be a genius when it comes to this stuff (far from it). Just from my end, I can’t see using a RJ-45 as a cable connector as being an impossibility, so long as you make sure it’s programmed well enough to tell what system is being used when signals are being sent to and received from certain pin combinations.