We currently do this exact thing where I work. And, I hate it.
- Lots of extra points of failure
- We're always short uplinks in the cabinet.
- When we need new links, someone is wiring in the cabinet on a ladder, risking all the other links.
- We have wire guides in place to clean up the wires below each patch panel and then wire guides on the switch side, wasting space.
- tripling the number of cables. Yay. I need more of those!
- And the bajillion patch cables run with no rhyme or reason and no way to easily trace them down.
That last point is the worst. When you are in a hurry, the multiple levels of trace-down are hell and your switch is far-far away when all you want to do is check the lights on the server and the switch at the same time.
If you do do it this way, On thing I'd recommend is that you interleave 1µ switches with 2µ wire guides so you don't have a mega-brick of wires running down each side from a block of uplinks to a block of switches. You have to tie the wire down to keep it under control once you have 200+ wires in one channel and then you can't trace ANYTHING down.
If you have SAN fabric that is a second switch then I'd put it at the bottom so your wiring goes different ways.
UPDATE with Advice
We used Panduit pop-in patch panels and the hard-wired both, either are fine if your electrician is good. Lots of stress relief is critical with long-term wiring, bend them, bundle them, and tie them. And, honestly, you have to instill a culture of doing things right... so get vertical wire guides and use them religiously. (Velcro to rack frame is fine!) Draped cables are cables gravity is destroying.
To @voretaq7's point: pre-wiring the entire block of 24 is a good idea you'll find uses for them later (we wound up pulling KVM, using them as cabinet-to-cabinet links and more.).
Work hard to keep things consistent. 1-24 should connect in order to 1-24 on the other end. If you've got the switch ports for it, pre-connect all of them (or half) in order as well. If you run more than data on ethernet, color code every cable for that link. You want to be able to spot the weird ones in a hurry. Consider assigning ports by rack µ number rather than loading from left to right. Anything that helps you avoid having a giant spread sheet full of chained addresses that people can't read in a hurry.
Once things are live no one wants to let you go back and make things consistent, so having easy, natural standards that people can follow in the emergency times without paperwork means you don't fall off discipline every time a server dies.