There's also the issue of verification speed, which with the current implementation of Cryptonote *is* an issue, though I think we both agree that it's "just" a matter of engineering. Again - it's nice that the WK design reduces the need for extra attention paid to high-performance coding, because trying to make things fast and correct is harder than just making them correct - but this is also something that can be resolved empirically.
We looked at this a little after someone complained about it, on this thread I think. It turned out that the biggest problem, by far, is not verification, but that the blocks are being delivered multiple (as in many) times during synchronization. We have someone assigned to debug it. Once that is fixed we can take another look.