Microsoft
MicrosoftGregg_H - Again, good questions. I would not say that I recommend LBFO, it's just your only option on bare-metal systems. Some customers do not require Hyper-V and wish to leave the system without it. In that case, LBFO is your only option. However those scenarios are dwindling between on-premises Azure Stack (and Azure Stack HCI), and Azure cloud opportunities. Quite honestly, i'm not sure that there is a true, measurable benefit to using a bare-metal host if that means you have to use LBFO.
Regarding S2D - Storage Spaces Direct team recommends using iWARP RDMA adapters. RDMA is one of those advanced features that doesn't work with LBFO. So if you're teaming your RDMA capable adapters, you MUST use SET. Furthermore, storage is generally considered a critical workload for most customers. Given my previous statement about stability, I would recommend that you install Hyper-V and use SET even if you're not running virtual machines or using RDMA on those S2D nodes.
In all scenarios where you can install Hyper-V, I recommend the use of Switch Embedded Teaming (SET) over LBFO.