I think I have a 1 TB drive that I can wipe, to see if I can install eCS.
It is not a hybrid, but I used DFSEE to clear the front end of the drive, then I attached it (as the only drive) to my A88MX-A motherboard. Then, I booted the eCS 2.2 b2 DVD, and installed eCS. The first thing was that the disk check found nothing on the disk, and put a partition table on it (as expected, and this is probably the critical step). Then, it needed a reboot, and got to the disk setup. It found no partitions (as expected), and started miniLVM. I then added the boot manager (AirBoot 1.1.0), and made my partitions:
300 GB for windows, bootable, primary, no drive letter.
50 GB for a FAT32 drive, bootable, logical, letter D:.
2 GB for the first eCS boot drive, logical, bootable, letter C:.
2 GB for the second eCS boot drive, logical, bootable, letter M: (no good reason for the letter M:).
the rest minus about 1.5 GB, for my data/programs disk, advanced, letter W: (no good reason for the drive letter).
the rest for a bootAble maintenance partition, bootable, letter Y: (no good reason for the drive letter).
Saved, and selected C: as the install partition. Formatted that as JFS. Then, I formatted the rest of the eCS partitions as JFS. The windows partitions are left not formatted, for now.
Then, I set up eCS on the C: drive, putting all of the optional stuff (%HOME%, %PROGRAMS%, CUPS, RPM/YUM etc.) on the W: drive. A few minutes later it was all done, and works with no trouble (so far). AirBoot did require a little adjusting, which is easy enough.
As I said earlier, the drive should always appear to be a normal drive to the software. All of the speed up should be done invisibly (but, I could be wrong about that).
Some other things about the motherboard:
I had to specifically select UniAud for sound. I don't think sound works, but the driver loads (no speakers).
I also had to install the LAN with the IBM NULL adapter. The available R8168 (8110) driver will not work, and it can turn off the interface so that even windows won't turn it back on. If that happens, you need to turn the machine off, pull the plug, wait for about a minute, then plug it back in and turn it on. The ONLY driver, that I have found, that will properly run the NIC is the newly released MMRE driver, from Arca Noae. The newest R8168 driver (from Arca Noae) works for a short period of time, but then it slows to a stop. Older versions probably trap.
I am also using QSINIT so that I can use the memory above 4 GB as a RAMDISK.