I see now you argument,
And it indeed works(we're now faster then range.aggregate for ranges with >12 elements, previously we were better for >20 elems).
But would it be better to specialize kernel.workOn to eliminate boxing for both sequential and parallel(workstealing) operations?
The same result will be achieved, but for both collections and with less code to maintain.