Yes, you have the global model, with MEA region. As for the boot.img, extract it from the same version you have installed. In this case, you have to extract it from RMX3301export_11_A.15.Alright forgive me if I sound like a noob because well I am, but if I do 'adb shell getprop' among the list I get [ro.product.odm.name]: [RMX3301] and [ro.build.oplus_nv_id]:  which obviously differs from what your showing above for the EU version. So it is safe to say I have the Indian/global version? Odd that it would ship with an EU compatible charging brick.
I also show [ro.build.version.ota]: [RMX3301_11.A.15_0150_202204270128] and
So given all of that I should be okay to pull and magisk-patch the boot.img from the IN A13 rollback package RMX3301_ROLL_BACK_Android12_IN.zip from here? https://download.c.realme.com/flash/DP1_Android_13/IN/RMX3301_ROLL_BACK_Android12_IN.zip
When I downloaded the EU rollback a few days ago I got the IN rom RMX3301_ROLL_BACK_Android12_INRMX3301export_11_A.15.zip instead, however I just re-downloaded it and this time it was the proper EU rom RMX3301_ROLL_BACK_Android12_EU.zip. Someone must have linked the wrong file at first and so wanted to make sure you're not comparing that originally linked roms boot.img because it would be the same as the IN boot.img since it was the IN rom in the first place not the EU.
Edit: Keeps bugging me that I got an EU charging brick. IIRC I read somewhere that OTA updates can differ when connected to a VPN for various regions. Could realme have changed my phones ROM/model version when I did my first OTA update since I am not in the EU? Oh nvm looks like you're in the US as well so if that was the case then yours would have been changed too.