Regarding wallet updates, may be change the pinned thread subject from "Bitcoin Core 22.0 Released" to "Bitcoin Core wallet update Releases" etc... and you can keep posting the updates there only 
It would get too messy and confusing with new versions.Always the new update threads like this 23.0 thread untraceable unless one go in to the last post under the pinned thread and no one will go there by seeing the subject as 22.0 (old) releases.
I've asked an admin to sticky this thread and remove the 22.0 one, as I usually do for each new release.Any reason for this?
Just due to me playing with nodes all the time I actually use it a far amount.
The issue at least for me is that on some older / slower devices there can be a LONG delay between when you start the daemon and it actually is ready to respond to a command.
-rescan was a 'fire and forget'
We're trying to move away from having a load of startup parameters and default startup actions for all the wallet things. IIRC rescan on startup also locks out a bunch of functionality until the rescan is done, and if you have multiple wallets, it would rescan them serially, not in parallel. rescanblockchain is also more flexible.Just due to me playing with nodes all the time I actually use it a far amount.
The issue at least for me is that on some older / slower devices there can be a LONG delay between when you start the daemon and it actually is ready to respond to a command.
-rescan was a 'fire and forget'
You can achieve the same by having a script call rescanblockchain for all of the wallets and then set that script in the -startupnotify option. This will execute that script once startup is completed.