Comment 8 for bug 2027613

I'm happy that it seems to solve all your cases

I do not think that remaining concern of yours is a real concern we need to have.
That is the standard behavior and usually "unless you have a reason, you want to be normal".
Here an example of a service people consider mundane:

root@m:~# apt install apache2
root@m:~# systemctl status apache2 | head -n 3
● apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; preset: enabled)
     Active: active (running) since Mon 2023-07-24 06:04:24 UTC; 1min 29s ago
root@m:~# systemctl stop apache2
root@m:~# systemctl status apache2 | head -n 3
○ apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; preset: enabled)
     Active: inactive (dead) since Mon 2023-07-24 06:06:15 UTC; 2s ago
root@m:~# apt install --reinstall apache2
...
root@m:~# systemctl status apache2 | head -n 3
● apache2.service - The Apache HTTP Server
     Loaded: loaded (/lib/systemd/system/apache2.service; enabled; preset: enabled)
     Active: active (running) since Mon 2023-07-24 06:06:34 UTC; 5s ago

So it behaves just like yours.
Remember, stopped services would also come back up on reboot.
People know (or need to learn and understand) that "stop" really just means "stop now".

And your own tests confirm that "disable" does well what it is intended to do.

It is up to you, but my gut feeling says that with this current proposed solution it would be good?
If you agree you want to get that uploaded to mantic and then augment the ongoing SRUs to include the same.