I have a SB3 now myself.
I had thought about modding the SB3 and the Transporter. I will be modding a few SB3's for customers, but not the Transporter. The only reason to buy a Transporter is to use it for the analog outs, and I dont care for the D/A chip used in there.
I have decided not to mod my SB3, except for a minor mod: Adding a clock input so it can act as a slave device. If I do this, then the power supply and even the jitter coming from the S/PDIF out is a dont-care. This is because I will be sending the S/PDIF signal to my Pace-Car reclocker. The reclocker acts as a master clock for the SB3 and buffers the received data in a FIFO. It also isolates the ground between the SB3 and the audio system. There is really nothing from the SB3 that needs to be perfect, the power can be crappy, the S/PDIF signal can be jittery, the S/PDIF cable can be cheap, and even the ground can be noisy. It will still have squeaky-clean, low jitter digital output from the Pace-Car, as perfect as it can be. The Pace-Car output will be I2S because it just makes sense. Converting it again to S/PDIF or AES will just add jitter back in. I should have the Pace-Car ready for this application mid-summer. The only downside is that it will only do 16/44.1. I'm hoping for a SB4 that will do 24/96 like the Transporter. This is the only thing (except for SRC upsampling) IMO that is keeping networked data streaming from being the best quality source possible. I believe this combo will even beat the mighty Memory Player.
Steve N.