This solution is somewhat unsystematic. For the same reason, we would then have to duplicate a lot of other properties where we have the same problem. "Creator" and "Creator name string", "Architect" and "Architect name string", "Discoverer or inventor" and "Discoverer or inventor name string", "Street" and "Street name string", "Surname" and "Surname string", "Given name" and "Given name string", "Location" and "Location name string" etc. etc. Virtually every property which refers to a specific entity that has its proper name.
An elegant solution would be an combined text/item datatype, which enable to enter both, either the item link or a character string. Of course, tools would still need to be developed that could additionally transform a string into a link as soon as the item were ever created.
There are several ways how to construct the combined datatype. One of them is to switch string/link modes, the second one can be to create automatically some virtual/temporary items, which would be similar to disambiguation pages.
This taks has relation to the T107693 task (both are related to the cases where the target item doesn't exist). Sometimes it is better to create such an item, other times not.