What a hassle! Glad you got it going. A few observations, albeit too late (sorry, I'd missed the thread):
1. I would not use an SSD for my boot or swap devices, both of which are typically on drive C:. The advantage of an SSD is its blazing speed, but it has one disadvantage over Winchester drives: its storage capacity is slowly reduced over time, the rate of which depends on how often it's written to. If it hosts the swap drive, it'll get written to a LOT.
2. But since you've already got the SSD in place as the boot device, you can alleviate this problem by moving the swap space to another disk. Don't worry about performance; your 16 GB of RAM will help assure that page faults are minimal. (You could even get another SSD and dedicate it to the swap file. It can be the smallest, cheapest one you can find.)
Windows 10 really buries this feature...go to the Advanced tab on the System control panel applet and click on Settings, then to the Advanced tab of that dialog and click on "Change" under "Virtual Memory". When you finally (whew) get to the Virtual Memory dialog, you can specify a different disk drive to host your VM paging device.
3. I have to admit I've never replaced the C: drive with an SSD (which I'd be reluctant to do anyway), but I have had many occasions to replace the C: drive with another hard disk. Each time I've done that, I have kept the original drive installed under a different drive letter. There are several advantages to doing that. First, you have an alternate boot device ready in a pinch. Second, all your old files are there to be easily copied over to the new drive (you will always remember something you forgot to copy, sometimes months later). Third, once you're done with the old drive you can delete what's on it and use it for additional storage such as project and library backups, or to host the swap space.
4. There is very little advantage to using an SSD for drivers, or for anything else that loads once and stays resident in memory. We're talking about a couple milliseconds at boot time. If you have important files such as drivers on the old drive, it's perfectly OK to leave them there (unless you've had problems with the old drive and are no longer confident it's reliable).
Similarly, running SONAR from the old drive isn't a big deal, either. How long did it take to open SONAR on the hard drive with no project? 2 seconds? How many times a day do you do that? Once or twice? Is it worth the bother to save 2-4 seconds a day? Read one less forum post per day instead.
The big time savings is going to come from files you either read many times or are very large, e.g. project files and sample libraries. Those can be moved to the SSD, assuming it's big enough to hold them all. They do not need to be on the same drive as SONAR.