Hi Rodolfo!
Here you're not quite right, I guess. Making a move doesn't normally delete the hash, it "ages", some entries are overwritten, others are kept of course.
The aging of hash is one of the most difficult and from engine to engine different point in engine- programming, e.g. Mark Lefler once wrote in an email to me, he wouldn't want a "Keep Hash"- feature for komodo at all, but even as for engines where you have that feature, e.g. Shredder, if not activated (Shredder has that UCI- Option to chose) the hash isn't "deleted" by making moves ony neither.
But I'm rather sure too, asmFish has a problem as for communication with some GUIs and for it's Save Hash- command.
There aren't any valuable entries stored by "Save" nor reloaded by "Reload", even if the file is stored and shown in Win Explorer in chosen bigness, and Shredder13- GUI even does count down the amount of stored and reloaded data.
Yet time to solution for tactical positions with difficult to find solution is nowhat better after Save and Reload.
That problem is well- known as for komodo since a long time too, you can't store hash in Fritz- GUI e.g., Mark Lefler knows about the issue, he too says it's the GUI's problem not the engine ones.
You can store hash with komodo in Arena or Shredder, this one file you can reload then in Fritz too, (don't forget to "Delete Hash" before reloading the stored one or restarting the engine ((changing it or srarting the GUI newly works as well as "Delete Hash", maybe "Save" or "Reload" does so too as for the engine- communication with the GUI
) than time to solution of an already "found" hidden one is practically zero (as well as not changing the engine nor delete the hash by command) after reload and that's how it's meant to be, everybody can try out easily.
AsmFish doesn't store valuable hash- entries by save and reload, not in Fritz14 nor in Shredder13, about command- line- engine I can't tell , didn't try that neither