Difference between Replication and Erasure coding techniques
Erasure coding, commonly used in RAID parity stripes, consists of high-availability through computation of parity and striping the resulting data across multiple storage subsystems (or disks).  Replication, more commonly known as mirroring, simply writes multiple copies of the data to more than one storage subsystem or disk.
Erasure coding incurs added latency for all writes because the incoming data must have its parity computed and written to disk.  Reads under a failure mode are going to be slower since the missing data must be reconstructed on-the-fly by comparing the non-missing data against the parity blocks.
Writes under replication are typically not affected as much as under erasure coding since the replicated data can be passed through to the underlying storage without requiring a parity calculation, and is typically written to two or more disks simultaneously in parallel.  Reads of replicated data under a failure mode are typically the same speed as reads under a non-failure mode since the data is read from the non-failed disk in it's entirety without requiring any calculation be performed to &quot;make up&quot; missing data.
Erasure coding typically requires less storage space than replication because the only redundant data is the parity code, whereas in replication all the data is duplicated.
Arguably the most commonly storage redundancy scheme used in SQL Server storage systems is RAID-10, which uses a combination of RAID-1 (replication or mirroring in the more common vernacular), and RAID-0 striping without parity.  A typical RAID-10 array might consist of 8 disks configured into 4 mirroring pairs, where data is striped across the 4 pairs of disks.  This enables both fast reads, and fast writes, while maintaining redundancy.  More than a single disk can fail without data loss as long as any two disks in a single mirroring pair don't fail at the same time.

Logical Disk:            C:\
                          |
Striping:    ============================
             |        |        |        |
Mirroring: =====    =====    =====    =====
           D   D    D   D    D   D    D   D
           i   i    i   i    i   i    i   i
           s   s    s   s    s   s    s   s
           k   k    k   k    k   k    k   k 
           1   2    3   4    5   6    7   8

In Raid 10, up to 4 disk failures could occur in the above setup as long as no two failures occur in the same mirror pair.  With RAID-50, using erasure coding at the striping level, up to 5 disks can fail as long as only a single mirror pair has two disks fail simultaneously.  For instance, Disk1, Disk2, Disk3, Disk5, and Disk8 could fail simultaneously without data-loss.
To answer your question, any I/O that incurs extra operations over-and-above writing the data to a single disk in a non-redundant manner is going to add apparent latency to the system.  Whether one system is slower or faster than another depends greatly upon the actual implementation, with the optimizations made by each manufacturer varying greatly with target audience.
It's likely safe to say that parity (erasure coding) is slower, requires more I/O, and has a lower cost-per-GB than replication.  Replication is likely faster to rebuild, has lower write-latency, and costs more per GB.  Again, these assumptions are broad generalizations and depend on implementation details that vary by vendor and target system.