In one experiment here, I installed a fresh copy of Windows 10/Pro on a completely "cleaned" SSD. The source for my install image file was a Microsoft download. The installer package placed the Recovery partition as the first partition on an NVME SSD.
Also going back to Windows 2k era or there abouts, Windows installers write partitions not just on the drive you might be installing to, they write partitions to any other drive found in the system. Mainly because I want each of my system installations to be independent and self-sufficient, before I start an install I'll remove all other drives from the desktop.
With UEFI the partition allocation, stuff also gets looked at the by a system's BIOS so it can look for recovery partitions and possible boot partitions. But if another drive has another system's recovery partition written to it, losing that drive can make it impossible to boot that system. I prefer using the UEFI list of bootable systems over say Linux grub loader or Windows boot options. If I'm not careful, Windows 10 and 11 seem to make their own partitions the only boot choices.
The following Microsoft document does a decent job of explaining partitions and how to manage them.
Windows Setup: Installing using the MBR or GPT partition style
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style?view=windows-11
One reason for wanting to have 3 distinct systems installed is to be able to test new systems like Windows 11 and Windows 10 before this. From my point of view it took more than 5 years for Windows 10 to become usable for my purposes. Windows 11 has not yet reached this point. I need to be able to use something else when a new Windows 11 changes/deletes some capability that I rely on.
art