+1 from me; this is really necessary to ease the pain of this transition.
Clearly this is now too late for buster which is a real shame since this is
where the (really neo)mutt → mutt|neomutt transition will bite for most users.
There are lots of other tools that hard code "mutt" (e.g.: bts in devscripts,
and I think reportbug), so much so that attempting to use just the neomutt
package and not have mutt co-installed is painful (and local aliases, or
bash functions etc will not resolve those cases; although a symlink in ~/bin
or something in $PATH does).
I've given up attempting to have mutt and neomutt coinstalled and using the
same configurations happily, there's too much variation. Which also means
that my previously-working muttrc stuff for the really-neomutt mutt package
will break horribly when pkg:mutt becomes not-neomutt when those systems
are upgraded.
Argh!
