Thanks jphughan, this helped me on a slightly different issue that you might want to add to your notes should someone else have similar problems.
I've recently built a new workstation running a Ryzen 2700X on an Asus Crosshair VII Hero motherboard. I upgraded to the latest BIOS as of this writing for the board (ver. 1201), and installed Windows 10 setting up two NVMe drives in RAID 0 for the OS, and another 4 SATA drives in RAID 10 for data. Installing windows required adding at install time three additional drivers - RCBOTTOM, RCRAID, and RCCFG. Per the instructions from Asus, the individual physical drives showed until I loaded RCBOTTOM, then the raid volumes as configured in BIOS appeared as I loaded RCRAID.
Following Asus instructions, Windows 10 installed fine and my various RAID volumes were all accessible as needed. I installed Reflect and built Rescue Media using a USB stick. When I booted from the drive, none of my drives (physical or raid virtual) would show as either source or destination.
While trying to figure out what was going on, I noticed that only RCBOTTOM was listed in the list of drivers included in the Rescue Media build. None of the other drivers that I installed manually during Windows installation were listed. For some reason or another, it seems that the Rescue Media build process is not picking up the RCRAID driver, which is needed to see the configured RAID volumes.
I was having a hard time finding how to add drivers manually until I found this thread (easy once you know how). I added the RCRAID folder from the drivers I used during Windows install to the disk drivers area on the Macrium c:\boot directories. Rebuilt the Rescue Media to a USB stick, and gave it a try. My RAID volumes all show as expected, and I was able to copy a drive image of my system volume over to my data volume.
I don't know if this will apply to other using AMD raid drivers, but though I'd document it here should others have similar issues.