It is, yes. You can simply self-sign and then tell users how to bypass the security warning, which is what you're already doing so what's the problem?
It's a common misconception that macOS forces all software to be signed by Apple. It doesn't. ARM Macs require all software to be signed, but crucially, any signature is OK at the kernel level. It's only at the first-run-from-finder level that Gatekeeper gets involved. This has been true from the start and I've seen over the years scattered comments from Apple developers that they view the Mac as a true general purpose computing device, and thus have no plans to change this. The ramped up signing requirements on ARM are more to do with simplifying the core OS by ensuring all code has an identity than stopping non-Apple approved software.
If you think users should trust you despite your anonymity then you can simply point them to Apple's official documentation on how to work around Gatekeeper:
https://support.apple.com/guide/mac-help/open-a-mac-app-from...
The process is straightforward if you know about it:
1. Download a self-signed or unsigned app.
2. Locate it in the finder.
3. Hold down the control key and right click it, then choose open.
4. Click open when the security alert appears.
Most people think you have to use the command line to open non-signed apps on macOS but it's not actually the case.
To self-sign an application you can generate certs using the Certificate Assistant in the Keychain Access app, or use OpenSSL from the command line. Then sign as normal. The fact that the cert doesn't come from Apple means Gatekeeper will ignore it, but, allows the app to run on ARM and ensures the OS has a stable identity it can use for assigning permissions across upgrades.