Restoring data into a replicated table after failed purge process
I'm going to assume the table in question is a replication publisher, not a replication subscriber (since you shouldn't be changing data in table that has been replicated from another source).

While you can just delete and then re-insert all the fixed data on a replicated table, if it is large enough that's going to generate tons of commands to replicate over to the subscriber, which (in environments I've worked in) may take hours or days to sync across. 

So it is usually much easier to:


Remove the table from replication
Fix the table data, via bulk inserts or updates or SSIS or however you want
Re-add the table to replication
Do not re-initialize the subscription (you just want to snapshot that one table, not the whole database)
Run the snapshot job. It will push a snapshot of just the newly re-added table.
Run the distribution job


One further note: if you have already clogged up your replication with 100 million pending delete/insert/update commands, you can still execute these same 6 steps. The moment you remove the table from replication, all those pending records for that table will disappear from the queue, this usually happens very quickly and will cause a bogged-down subscriber to spring back to life.