I looked into the possibility of allowing NeoShare to work with hashes other than a Neo Hash and i see a few problems with that:
aside of more publishment overhead, and additional code complexity etc...
the main issue i see is with multi files,
NeoShare is strongly NeoKad based and relayed on NeoKad for hashset exchange and metadata exchange.
So if 2 neoshare clients talk to each other thay can no exchange a hash set or a multi files meta data, they relay on one of them publishing it into kad and the other one retrieving it from there.

Without a NeoX hash we can not store metadata (multi file structire/subfile list) in NeoKad,
so for torrents we would for example need to publish the entire torrent into kad and thats not so cool...

What would be some practical use cases where such a functionality would be really needed?

should be fixed but keep in mind that it may take some time to search for all as there is a limitation to 10 kad operations in total at one time.
you can open th eneokad exe manually befoure neolaoder to view the gui