Whats the deal with calling macOS "iOS", they are built on similar foundation, and the same kernel but certainly aren't the same, just saying..
As for why it doesn't work - well, first of all the error massage you've seen is related to a process called notarization which is required for a couple of years now and basically registers the fingerprint of the app with Apple so that they would be able to black list it if they want.
But notarization isn't the root cause of the issue here, the app is most likely compiled for 32bit architecture, something Intel Macs do support in hardware, however the support for it it was dropped OS wise to push vendors to recompile their software to 64bit, as a preparation to the Apple Silicon architecture that came out a couple of years later and included hardware assisted emulation for 64bit apps (amd64).
I've attempted to somewhat backport 32bit support based on Mojave on top of Catelina and had success when it comes to CLI tools, I was even able to patch the window manager enough to accept most of the deprecated calls, however there was just too much difference to be able to fully run the complex GUI app I tried to execute.
What does it mean?
The good thing - it usually just a matter of recompiling the app for 64bit and notarizing it with apple.
One could use virtual machines to run an older macOS version on intel Macs, otherwise you could use Microsoft's software based 32bit emulation for Windows on Arm which can also be run on an Apple Silicon Macs.
The bad thing - You won't be able to use the current version on modern macOS or any Apple Silicon based Mac, ever and the solutions suggested above are either cumbersome or require Ecotech to invest some time (hour tops, tbh).