Attached pictures of disk manager and uniqueid disk from diskpart, as you can see both have same uniqueid disk values.
A ramboot may (or may not) actually boot a volume "only".
Windows differentiation is (or at lest was) based on disks (not volumes) ID's.
Likely in your case of ramboot (cannot say if specific to the SVBus or not) the disk on which the boot volume resides (which is the VHD) is *somehow* not considered a "real" disk.
It seems it's in fact the opposite:
Having a uniqueid disk value on diskpart seems loaded on Ram as a disk.
All the internal HD partitions/drives are not colored (as this identify real drives I assume), but the one on Ram (X:\) is also not colored, so it seems it's "seen" as a real drive too.
The drive with a blue mark on top is the attached VHD, same way is shown when attached on the real OS. I assume this blue mark is then used to identify virtual disks.