>>529507218
My brain's a bit foggy atm, but the biggest downside I see is the combinator-crusher hard-wiring.
The biggest benefit of throwing all recipe signals onto a single control wire that hooks up to all crushers is scalability — you just chain-link the crushers.
Also what >>529508851 anon said. The solution I posted relies on throttling chunk input via grabber filter setting.
The real bother here is the reprocessing recipe. It collides with chunk processing recipes since they too produce chunks.
You have to explicitly send the specific reprocessing recipe.

Okay, after some editor fuckery I'm dropping what I came up with. Mind you, I might well be retarded.
>Asteroid collector
Collector:filter = constant (M,C,I)x10 - (Read crusher loop + loop-crusher inserter:read:hold)
This throttles the chunk input via collector filter setting. Protects the belt from oversaturation.
>Crusher
Crusher:recipe = sorter[0]:descending {
reprocessing:M => Hub:iron < constant(iron)*100 AND (Read crusher loop + loop-crusher inserter:read:hold) > constant(M);
reprocessing:C => Hub:carbon < constant(carbon)*100 AND (Read crusher loop + loop-crusher inserter:read:hold) > constant(C);
reprocessing:I => Hub:ice < constant(ice)*100 AND (Read crusher loop + loop-crusher inserter:read:hold) > constant(I);
Each:constant(iron,carbon,ice)*100 - Each:hub
}
The main course. This unholy abomination is my solution to the problem of reprocessing the excess chunks without causing problems with (lack of) other products.