I'm curious why resetting the database is such a bad idea?
Because not all MC fields are stored in tags, so you will lose a lot of data. If you start again with an empty database you will have a lot of work ahead of you. If you try to keep all the Custom fields and Views you may have created over time by deleting files out of the Library, then MC's process to recover all field data for deleted files comes into play.
It is far better to identify and fix the underlying problem. Perhaps that would help avoid it in the future as well.
Look at the Tag Dump area in the tag window to see if you can spot any problem. Search the forum for "Tag Dump" if you don't know how to do that.
Sometimes a file will have both a "Title" and "Name" tag, so MC needs to pick one. It just seems very unlikely that MC would swap field values around, or a whole lot of people would be complaining. There are some tools that allow examination of the raw tag information, though I can't think of them right now. Maybe viewing the raw tag and their naming would show something. Windows Explorer is a very unreliable tool to check tags. MP3Tag would be better.
Perhaps share a track or three that exhibits the problem, and we can see if it occurs when we import them.
Finally, your workflow is very convoluted. dbPa > iTunes > MC26. I would at least go dbPa > MC26 > iTunes, although I just rip in MC these days. Sure, the metadata isn't always there, or as good as dbPa, but I no longer use any other tools for ripping, tagging, or playback. Maybe I should, but MC works fine for me. I left the evil Apple empire a long time ago!