I don't think the nvme config is needed as doesn't seem to be included with other working distro's with nvme.
I don't think it is working from labels you know, even though root is labelled root.
In the uboot env the only label mention should be rootfs not root but it still loads.
I think basically it just runs because it is at the end of the 32mb loader partitions and the root folder is positioned normally where the boot partition is but here its an all in one.
That is the biggest problem as the seek point for /boot is in the root so can not be separated and prob will hinder as dropping that root will also drop the boot partition.
Thinking it prob needs to be like the others with separate boot and root partitions, its actually really good that way as if we ever do figure out how to get the uboot console on hdmi then you can multiple options and multiple roots parts if you ever wanted multiboot.
I am going to chance my luck at changing the nvme label to rootfs as you never know but thinking as an all in one its likely not to work.
I am trying to remember where in the kernel load the rootfs comes in.
I was wondering more where the labels are used in the uboot env as can not seem to find them.
Yeah I changed the label for the emmc from ROOT to boot
Changed the label for the nvme to rootfs
Changed the uuid of the emmc partition to a generated one and then the mentioned one in the uboot env B921B045-1DF0-41C3-AF44-4C6F280D3FAE
Didn't think it would work but the thing that makes me think because the isn't a separate /boot /root partitions it just accepts the default seek point of the partition start as default.
As after changing both label and uuid it still booted as normal.