[Magisk] pndwal:
I took a look at your highlighted code linked in this original post and it seems you've simply misinterpreted this from the start... It all indicates tests will give Ramdisk = Yes for your device just as Magisk was telling you and as I've been telling you is totally expected!... I don't know why you think "But those tests do not reflect the truth in this case (they say Ramdisk no)", or why you "kind of expected for this one to read "Ramdisk no" or were 'surprised to see "Ramdisk yes" '... You just need to let go of your assumptions and understand original Android booting architecture and how it's changed with SAR and further with 2SI...

If you had read what I've already told you more than once I wouldn't be repeating this.

The original Android boot method, 'legacy ramdisk', used the kernel uses initramfs (ie. the ramdisk section in Android’s boot image) as rootdir ALWAYS! Ie. Ramdisk is ALWAYS "Yes"!...

Your device, Motorola Moto G (3rd gen), launched with Android 5.1.1, OBVIOUSLY uses ramdisk in /boot!

ALL Android devices used this method until the SAR devices appeared, the first being Google's Pixel (first model) launched with Android 7 with a new boot method: Kernel directly mounts the system partition as rootdir so a boot ramdisk is no longer needed or supplied.

... Of course this and other 'legacy SAR' devices with A7 or 8 were ALL A/B 'dual slot' devices anyway and these still retained a usable recovery ramdisk in /boot (this was moved there as these A/B devices eliminate /recovery partition) so Magisk began to hijack that for booting to system with root (boot mode Magisk). Magisk works happily in the recovery ramdisk in boot partition/mode.

The first A-only Legacy SAR devices launched with Android 9 and were the ONLY devices that EVER lacked ramdisk in /boot partition (apart those launched with Android 13+ which now puts generic ramdisk in /init_boot instead) as the recovery ramdisk is in a dedicated/recovery partition just like legacy ramdisk devices.

With the introduction of Android 10 and '2SI ramdisk SAR', the kernel once again ALWAYS uses initramfs (read ramdisk) as initial rootdir, so Ramdisk = Yes indication appears for ALL A10+ devices too.

A/B 2SI devices use the recovery ramdisk (still in /boot partition) for first stage init using a method Google officially calls 'BOARD_USES_RECOVERY_AS_BOOT', then execute /init in rootfs to mount the system partition (second init stage) as the new rootdir before executing /system/bin/init to boot... Magisk injected in the recovery ramdisk also works fine for boot mode root with 'BOARD_USES_RECOVERY_AS_BOOT = true' (A/B) devices... A-only 2SI devices use the a normal boot ramdisk for first stage init, then execute /init in rootfs to mount the system partition (second init stage) as the new rootdir before executing /system/bin/init to boot... Magisk injected in this boot ramdisk works fine for boot mode root (with 'BOARD_USES_RECOVERY_AS_BOOT = false') in A-only '2SI ramdisk SAR' devices too.

If you wish to understand Android and Magisk booting/init methods, including Ramdisk indicator in Magisk App, PLEASE don't disregard these basics (again)!.. Please do yourself a favour and take time to digest this!!

Links are in my previous responses to you. 🙃 PW