No, that’s not why. It’s just the combination of Blender and Python. It’s the same on Windows. Blender updates semi-frequently, so sometimes add-on devs don’t have the time to recompile their add-on for a new Blender release. If a user loves the add-on and updates to a new version of Blender, they may not be able to use the add-on in their updated Blender. As such, the user downloads/keeps an older version of Blender to make sure they can continue using that add-on.
In the case of Arch, we are now using Python 3.12. Blender 4.1.1 uses Python 3.11. This is the actual issue. So, you should be able to install Python 3.11 and run the system installed Blender with no issue.
That would be:
yay -S python311
I did not recommend compiling from source. I said it is “technically better”, but it is recommended to use the official repos for your distro.
The reason Debian/Ubuntu packages are common is because that packaging format was/is king in the Linux world — at least in the eyes of app devs. So, sometimes if you check the build information for even Arch’s official packages, you’ll see it reference a .deb file or Ubuntu.
Regarding compiling from source: until you become very advanced in using Linux in general, I’d recommend pretending that such an option doesn’t exist.
This recommendation is specific to frequently updated packages, however — Firefox, Blender, Krita, etc. For packages like qimgv, fsearch, etc. that get updated like once or twice a year, you can practice compiling and updating from source with these.