I've run the concurrent-by-tx confirmability checks both after completing download and during download. Interestingly there is almost no increase in total download time, 5-10% at the most but this is within the typical range of download variation. 840,000 blocks are downloaded and archived in 69 minutes while at the same time the first 381,395 have been checked for confirmability. The total run completes in 2.5hrs, which is slightly faster than if all confirmation is performed at the completion of downloads. Notably, confirmation reads a huge amount of data (and writes very little). So on low memory machines it will suffer, and performing it during download is likely to produce terrible page churn.