Rollback to stable cleans the history store even for the tables that are timestamp and immediately durable in scenarios when those tables are never checkpointed. As in those scenarios, the durable timestamp that is zero, so it treats as a non-timestamped table and performs the history store cleanup that can lead to data loss.

The solution to this problem is to avoid cleaning the history store when the tree is modified.