SQL Server Replication with Historical Tables
Is it possible to replicate a SQL Server database and for the replica to have temporal/historical tables?

Yes.  If you use an AG Replica, the primary database and replicas will all have the same Temporal Tables.
If you use Transactional Replication, you can have a Temporal Table at the subscriber, where the table at the publisher is non-temporal.
If you use Change Tracking or Change Data Capture you can use the change data to ship and apply to a temporal table in a reporting database.
See

Usage of replication technologies is limited.
Always On: Fully supported
Change Data Capture and Change Data Tracking: Supported
only on the current table
Snapshot and transactional replication:
Only supported for a single publisher without temporal being enabled
and one subscriber with temporal enabled. In this case, the publisher
is used for an OLTP workload while subscriber serves for offloading
reporting (including 'AS OF' querying). Use of multiple subscribers is
not supported since this scenario may lead to inconsistent temporal
data as each of them would depend on the local system clock.
Merge
replication: Not supported for temporal tables

Temporal Table Considerations and Limitations