M.2 PCIe drives may be in wrong slots

Version: 10.0.18363 build 18363
This is a very small issue, but because the boot disk is usually named “Disk 0” under the Disk Manager, I must pay extra attention to disk names when doing full-disk O/S backups. And since the contents of the cloned Backup disk are supposedly identical to that of the boot disk – how to tell which version is be used at start-up.

When Sager built this notebook, they may have installed the O/S M.2 PCIe disk in the wrong slot. Then after receiving notebook, I installed a second (and identical) M.2 drive in the other M.2 PCIe slot. When I checked the Disk Mgr screen, the factory installed M.2 showed up labeled as “Disk 1” while the one I later installed was labeled “Disk 0” – which led me to believe that M.2 slots may be hard-wired to specific addresses known to the POST, registry, et al protocols -- so that the physical slot location determines the assignment of the disk number: 0,1,2,3………

Since both M.2 drives are now populated, is there any risk of messing up the protocols (POST, Registry, BIOS, etc) by switching the M.2 drive slot positions? I fear that somehow upon factory initiation/activation, M.2 slot number “Disk-1” was designated to the system as the boot drive. So that maybe at start-up the system will boot from the clone Backup copy instead of the original boot disk, if I switch the drives slots.

Caveat: I know just enough about the technical aspects of system to be dangerous. Anybody with knowledge of this disk assignments? Although I am comfortable leaving them as is, but more comfortable if the boot drive was Disk-0.
See attachments for details.

Thanks to all who have responded to this thread; I learn more and more each time I visit Forums here. But one last comment as to my concern to change drv# (which I will NOT do). Because I use Casper restore softw from FssDev.com to backup OS sys files on all my past computers.

I'm careful not mix up the source drv# with the destination drv# when following the BKP dialogue in Casper. And to make it more sticky is that Casper dialog auto designates the "C" drv (OS) as disk#1 (not disk#0 which in all past computers using Win7 was always Disk 0 which was the OS and sys drv.

So when my new Win 10 system labeled OS "C" as disk#1 instead of like all past systems as disk0, now I have to pay more attention to Casper dialog when doing BKPs. Not a big at all, but I too often get distracted with more multi-tasking and prone to make errors like swiping the "C" drv by accident. And this is why I briefly entertained to possibility of changing drv numbers -- just to make Casper backups more routine to old habits. It was more of a convenience than an issue. But thanks for all the comments! Mike