“The Hybrid Kernel is a mix of Monolithic & Microkernel - takes the best from each to improve performance and avoid the drawbacks.”
Since you’ve already quoted Linus Torvalds, who actually knows enough about this to have written his own operating system kernel, and then you disagree with him - maybe you can explain what it is about Haiku’s design that makes it a “hybrid” and proves him wrong. For example, how does Haiku avoid the most obvious and serious drawback of a monolithic design, the fact that a bug in a filesystem, network protocol, or hardware driver can crash the OS or corrupt unrelated data ?
In fact can you point at any specific feature or set of features of Haiku and say “that’s why it’s a hybrid” ? If you struggle to do that, don’t you think you should re-evaluate your certainty that Haiku is a “hybrid” and even that this category exists ?
You say that OS X is an example of a “hybrid”. OS X runs as a single privileged OS server on top of the XNU microkernel. Apple got their experience of this approach by porting Linux to run on Mach in the same way, the result was MkLinux, the Linux kernel running as a privileged OS server on Mach on Apple PowerPC machines. MkLinux was not considered a success (people not unreasonably preferred faster cheaper native Linux on x86), but Apple’s engineers used what they’d learned when rushing to mash bits of FreeBSD, NeXT and other components together into what became OS X. Today’s Linux distributions for PowerPC don’t use MkLinux, but instead a perfectly conventional port of Linux to the native PPC hardware.
If that’s what a “hybrid” is then MkLinux was there in 1996, nobody was very impressed, and also, Haiku doesn’t resemble this design at all, it doesn’t have a microkernel (whether Mach, or L3 or custom built) underneath, it runs on the bare metal just like other monolithic OS kernels.