The issue here is that the partition "offsets", i.e. their size and positions on disk, are different between the Source and Destination disks. By default, Reflect restores partitions such that their size and position on disk on the destination matches the source. The Source and Destination disks in this case have very different capacities, so the scale of the partition layout table is misleading (though that's by necessity because otherwise a small disk might show unusable small partition blocks) but if you look at the sequence and total sizes of the partitions on disk, notice that Partition 1 through 5 on the Source and Destination match. So those can be restored the normal way without any issues. But then your Source disk has Partition 6, which is a Windows Recovery partition, whereas Partition 6 on the Destination is your R drive. So if you choose to restore Source Partition 6, by default it would be restored into space that is partially occupied by the R drive on the Destination, and therefore the R partition would be destroyed -- hence the warning. The way to restore a partition such that it does NOT maintain the same size and/or position on disk on the Destination as it did on the Source is to drag and drop the source partition onto a desired existing Destination partition or into empty space on the Destination. The complication here is that your Destination disk is a bit of a mess. You have three separate Recovery partitions, namely 1, 7, and 8. The "legacy" location for Recovery partitions is Partition 1. But since Windows 10 evolved to require larger Recovery partitions over time. So the new method is to place the Recovery partition directly after the Windows partition, so that if it ever needs to be expanded, Windows can shrink the Windows partition by the desired amount. But even your Source disk doesn't use that layout.
If i were in your position, I would make sure I had a good image backup of the Destination disk shown in your screenshot, then delete both of the Recovery partitions at the end of the disk, then delete the Q and R drives, then restore the Recovery partition at the end of the Source disk into that space directly after the Windows partition on the destination disk, and finally restore the Q and R drives after that. That will still leave you with a redundant Recovery partition at the beginning of the disk, but reclaiming that space is a bit more of a chore. If you're not up for that, then I guess the best solution would be to drag and drop the Recovery partition at the end of the Source disk onto one of the two existing Recovery partitions at the end of the Destination disk. But you'll have to do that every time you perform a restore operation like this, and you'll still have a non-standard Recovery partition placement, and it's not even clear that any of your three partitions will work after that. Windows has a BCD entry for Windows Recovery, and it has to know which partition on disk is the Recovery partition. I have no idea what yours would say at the moment. @dbminter
Yes you can restore entire disks in a single operation, in fact that is the default mode of operation. What you cannot do is restore to multiple disks or from multiple source images in a single pass. You've been using Reflect since V4 and have only ever restored one partition at a time??