I don't know... I have very little understanding in this area aside from the "givens"
1) I really don't care if I have to install programs on a separate drive from where the OS is but my understanding is that it's a bad idea to do that (speed issues, etc...). Going for the fastest configuration
2) As a follow on to #1, speed may be a concern (the OS likes to talk "directly" to the programs on the same drive for best performance). Thought this was a basic fact but maybe something I learned wrong...
3) Making the OS think it's on the same drive as all programs (those installed on another drive) may get around any issue introduced by having them on separate drives... I just don't know...
4) I've never tried RAID, but assumed it's not that hard. Is it a bios config thing?
1-2) It doesn't matter if a program that's installed on one drive has to work with data from another drive. The program is loaded into RAM anyway. If at all it should have a small positive impact.
There are three ways of creating RAID volumes:
1. Hardware RAID: RAID is managed by dedicated RAID controller, OS only sees the RAID volume. Currently very expensive for Nvme drives.
2. Firmware RAID: RAID is managed by Motherboard firmware, runs on CPU, and is set up and configured in the motherboard's firmware settings. It might need drivers to be detected by Windows, which can makes Windows installation on such a RAID volume much more complicated.
3. Software RAID: Hard drives are kept transparent to the operating system. RAID is either an extra layer on which the filesystem is installed or part of the filesystem. On Windows the only way to do this are Dynamic Volumes. They are easy to set up in Windows Disk Management, but you sadly can't install Windows on one.