Trivially. Zip file headers specify where the data is. All other bytes are ignored.
That's how self extraction archives and installers work and are also valid zip files. The extractor part is just a regular executable that is a zip decompresser that decompresses itself.
This is specific to zip files, not the deflate algorithm.
That would be a big zip file, but would not take a long time to unzip.
There are also deflate-specific tricks you can use - just spam empty non-final blocks ad infinitum.
If you want to spin more CPU, you'd probably want to define random huffman trees and then never use them.