It's a minor change to workflow but as much a personal preference as anything. I personally wouldn't have an issue doing initial imports and adjustments straight to SSD, and when done, moving off to HDD. Library manipulations are going to be faster if everything on the SSD, but it's simply not realistic for current SSD capacity, usually. The things that do the heavy lifting will always benefit from the speed, even if it's just an in general 'feels faster' sort of way.

Generally you want your applications and OS on the SSD. Typically if you're opening an image to make adustments, the image is going to be in memory for the processing aspects, so where it's located pre-load really only matters for the initial load and then the save out. Yes, but with the caveat that it depends on the program. If I have to copy the picture files first onto the SSD in order to see PS speed/processing improvement, I wonder if it is worth for me using an SSD? (Since I really don't mind PS loading off an HDD taking 20sec, versus loading of and SSD taking 4secs. PS, does not run any faster by just being on the SSD? The picture files have to also be on the SSD to have any improved PS processing speed. Otherwise, opening/start-up/loading (what ever you want to call it) is the only place that you'd see improvement in speed. It would only 'run' faster if the data files that a program is reading or writing are also on the SSD.

How to use ssd for boot drive