Our bash support, even with those projects, is not as good as the other shells. There’s issues opened pretty much every week, and there’s only so much we can do without native hook support.
Unless ksh supports hooks (I don’t think it does), then it’s not really something we can support. It’s probably possible to get 60% of the way there with traps/etc, but it will never be that reliable.
ksh history is full organized around user’s history file, so directly shared between user’s sessions, without any memory cache mecanism, so very basic (and old) design.
Sadly for us, even on linux servers we use ksh as bash replacement, to be able to act in the same way on our Linux and UNIX servers.