Disabling the 'set' and 'dump' subcommands of 'history' as the session persisting doesn't make as much sense and those need to not be switched mid-run
Load and write session data at start and end. This means multiple sessions can overwrite each other. Older data will be saved over newer data.
Preserve the newer commands via a queue. Common commands can still be purged but newer sessions without overlap win over others