That is the key. As I said earlier, having a btrfs OS control grub by installing it “after” MX Linux, I had no issues as it incorporated other installs into its grub. It is when you try to install the non-btrfs after the btrfs OS and have it control grub that issues arise.
If @Skywalker71 has already been using Fedora and does not want to install it again, we have to use a work around in order for Debian to show Fedora in its grub menu.
So I had to add those symlinks and copy a folder from @/boot on that subvolume to the EFI partition of MX Linux. Then MX gained back control of grub and added the entry in grub menu for Garuda OS.
Sheila