Transactional Replication: Maintaining schema changes
With transactional replication you must ensure that your schema changes are compatible or risk errors on the subscriber.  In practice this means reviewing the schema change scripts and testing their compatibility with your replication topology.  Adding articles requires a new snapshot, but you can create a second publication to hold the added tables if you want to reduce the snapshot size.  

If you don't want to do that, then a log-based replica is probably a better design.  See, eg Read Scale Availability Groups