Another reason to keep drive letters the same is because your retention policy might eventually age away old versions using the no-longer-being-backed-up path, but this may or may not matter to you.
The database uses the full paths including the drive letter, so changing drives looks like a rename, but the deduplication will figure out that all the blocks of data in the new pathname are already uploaded.
This actually might not quite be answering your question. A Recreate almost certainly only rebuilds the DB from the backup files without worrying about what’s on the drive right now, and is basically what a Repair does if DB is missing, e.g. new import of job without moving the older-but-matching-remote DB.
Tries to repair the backup. If no local database is found or the database is empty, the database is re-created with data from the storage. If the database is in place but the remote storage is corrupt, the remote storage gets repaired with local data (if available).
sounds like a Repair that is not a recreate-from-scratch might work better without a drive letter change.