I am not speaking for or against the DNA -solving- these types of issues. That would be a whole different thread.
Just addressing how the presentation and use of the maiden name/married name and unknown surname affects different users of the ancestry product. And it affects results for some things, such as searching.
People who don't search from their trees would have a different experience with this than those who do. New search is affected more than old search. Searching your own large trees would be more trouble than small trees. It affects different users in different ways. And actually certain family names or some locations it is more of an issue. One town in England that I research only seems to name the women Mary, Anne or Elizabeth.
"I wish I could propose a universal solution, but I can not."
I know what you mean.
We are using standards that were set before programs like this were made. They work great for things that are display trees or on paper.
For me the ideal would have been to have had a field for maiden name and married name and have both show up in the name list but ancestry would be hard pressed to implement that at this point.