The issue isn't so much blackout (the segments are 120 degrees separated^), but that contact time is expensive and you don't get 100% of the uptime to yourself. The DSN is basically the only infrastructure we have for this sort of long range communication. There are only three stations and JWST is sharing time with a bunch of other missions including everything that's currently on Mars. Scheduling takes place far in advance.
The problem also isn't absolute storage space onboard, even if capacity degrades at a gig a year, it's whether you can drain it faster than you fill it. That said, there is likely to be some limit on hard drive space depending on what the current rad hardened solutions are. JWST is built on very robust and well-known hardware that has good provenance in space. For a LEO mission you might be willing to risk less tolerant components to get terabytes of capacity, but out there you want extremely resilient components and 68 GB is probably the balance. Sentinel 2 (an ESA Earth observation satellite) has 2.4Tb/300GB onboard for example.
Ultimately the missions planners budget for how much data they're allowed to stream back and they've figured out an amount that is acceptable.
But in general, yes. If you can write to a disk and ship it, that's a good solution. IceCube (South Pole) generates TBs of data. We send back 0.5 TB of critical data every month over a fast satellite link, crucial alerts and telemetry are sent over Iridium (24/7 avail) and the rest gets sent back to Madison (WI) on a plane each summer.
^ In theory this means that you can service three missions at a time though, if they're not all in the same direction.