An HSS private key repositioned within a tree it already holds now keeps that tree rather than regenerating one identical to it, an LMS Merkle tree being a function of the key identifier, the master secret and the parameter sets and not of the one-time index, so both the root of any hierarchy and any lower level whose parent has not moved share the node cache and public key of the key they replace while still encoding byte for byte as regeneration did, relates to github #2414.