if system versioning is done via innodb internal transaction identifiers, there is no way to replicate such table to have identical data on the slave.
In SBR replication will work and replicated tables will be usable, but they'll have different transaction identifiers. in RBR it won't work at all. And one could not bootstrap the slave by copying tables over.
All this, supposedly, can be fixed by using gtrid instead of innodb internal transaction ids. That is, by adding gtrid columns to the transaction registry table and storing gtrids in versioned tables.