I would say that the feature is almost there.
Already now you can load the new files and those from the same artist.
Like that you can select the already used artist name from the dropdown list in the tag panel if you use one of the older tracks as template for the new ones.
All other data probably has to be entered individually anyway (as it is a new album with new titles, individual track numbering, new cover).
A more generic approach where all input is stored in the database and then presented for the new files has its drawbacks IMHO:
when does a string become a template? Everytime a new string is entered with all its typos?
How do you maintain these templates? How do you modify, delete existing entries when you find out that they were not quite right when you check them again?
How long should a list of suggestions be? For bigger collections several thousand items will be added to a dropdown list. This will take quite some time to load and also to find the right entry.
Would you need some kind of fuzzy search to cater for cases like "Rolling Stones" and "The Rolling Stones"?
That is why I think that the already possible approach with template files or actions of the type "Format value" for often used strings is a good one. But as I don't know what the future will bring, let us see.
Oh, and here is a thread on a similar topic:
or the idea to create user-defined dropdown lists: