If you can encode the version as part of the key for every keys, then the answer is yes. To do this, you may use the VersionStamp feature, which needs 10 bytes, as the key prefix. Then you can delete all keys whose commit versions are less than a version (converted to a versionstamp prefix).
A versionstamp is a 10 byte, unique, monotonically (but not sequentially) increasing value for each committed transaction. The first 8 bytes are the committed version of the database (serialized in big-endian order). The last 2 bytes are monotonic in the serialization order for transactions (serialized in big-endian order).