If you trust 3rd parties, you can do a lot of other stuff - in your example I'd have to trust the hashes in the coinbase are for the correct macroblocks (something I'd still have to verify! Also with potential pruning of unneeded parts of blocks in the future it can be the case that nobody any more has complete blocks as they were minted). Why not just include a BitTorrent infohash instead in the coinbase?
![Wink](https://bitcointalk.org/Smileys/default/wink.gif)
All in all: Yes, such an option would be nice (I actually don't know if the client downloads a block + verifies it, then loads the next block etc. or if it loads + verifies asynchronously), but it most likely won't save the verification step in a 0 trust scenario.