The diskless vs hybrid choice looks bigger than it is. Both modes manage the same Windows image from the same server. Both keep one game library for the whole floor. Both put a seat back to a clean state when it restarts. The single thing that differs is where each PC loads Windows from: over the network, or from a copy of the image on its own SSD.
And you don't have to answer it once for the whole room. You answer it per PC.
What the two modes have in common
Start here, because most of the confusion comes from assuming these are two products with two ways of working. They aren't.
In both modes there is one image on the server, and that image is the only Windows install you maintain. When you want to change it, to add a driver or a launcher or a Windows update, you switch one PC into Super Client, make the change there, and save it back. The image keeps versions, so each saved change is a point you can return to.
In both modes a seat that isn't in Super Client is disposable. Whatever a customer installs or breaks during a session is reverted at the next reboot, and the PC comes back to its previous clean state.
In both modes the games and shared data live on the server and are managed there. One copy of each game, patched once.
Think about what that means on patch day. A big shooter drops an update on a Tuesday. You update the game once, on the server, and every seat in the room has the new version the next time it starts. It makes no difference whether seat 9 is a diskless PC and seat 10 is a hybrid one, because neither of them stores the game. On the question owners care about most, how many times do I have to install this patch, diskless vs hybrid has the same answer: once.
That's the whole operating model of CCBoot, and it's identical on either side of this comparison. If you've been reading hybrid as "diskless with something missing", set that aside. Nothing in the list above is missing from it.
The one real difference
It comes down to the first thirty seconds after the power button.
A diskless seat has no drive in it. It starts from the network, finds the server, and loads Windows straight from the image the server holds. The image never leaves the server. The client is a motherboard, a graphics card, memory and a network port.
A hybrid seat has an SSD, and that SSD holds a VHD created from the server's image. The PC boots Windows directly from that local VHD. Once it's up, it reaches the server for the same things a diskless seat does: the games, the shared data, and the management that keeps it in line with every other PC.
So in both modes the image is the server's image. In one the seat reads it across the wire. In the other the seat carries a copy.