Chainloading from other devices not working after 9.0.1

[glics]

Running Limine 9.0.1 up to 9.2.2, on a x64 UEFI system (Thinkpad T14 Gen1 AMD, AMD Ryzen 5 PRO 4650U).
Secure Boot is disabled.
Here's the relevant configuration:

/Windows
    protocol: efi_chainload
    path: uuid(FE8D3BBB-9AB8-433C-A3FB-42FA7D23DEA2):/EFI/Microsoft/Boot/bootmgfw.efi

Trying to boot this entry results in a reboot of the machine which starts back into Limine;
Works fine on 9.0.0.

Here's what I have attempted:

• Trying to boot /EFI/Boot/bootx64.efi results in the same reboot;
• Trying to boot any other EFI file results in the same reboot, including an EFI Shell and Limine's own .efi copied to the other ESP;
• Trying to boot using the hdd() command results in the same reboot;
• Copying bootmgfw.efi to the same ESP as Limine is installed on, and booting it as boot():/bootmgfw.efi results in a successful chainload (but won't boot windows without copying other files from Windows's ESP);
• Trying to boot any .efi file from the same ESP using boot() works;
• Trying to purposefully give a wrong UUID or path results in a panic message as expected (Failed to open image with path...), without rebooting;
• Updating the device's firmware makes no difference;
• Using efi instead of efi_chainload and guid() instead of uuid makes no difference.

I have another machine (also UEFI x64, a desktop) on which I wasn't able to reproduce the issue, it boots from other partitions just fine.
Assuming this is a setup issue, I'm not sure how to further diagnose the problem unfortunately

[Zesko]

It might be related to the rework of the chainloading procedure in the commit between 9.0.0 and 9.0.1.

I cannot reproduce this issue.