I can see how a sneakernet would work with both engaging in transactions and confirming transactions, although its use in mining would be dubious at best.
As a stop-gap, you certainly could use a thumbdrive which contains the blk0001.dat and blkindex.dat files from an active node to receive the confirmations and come up with some system to store transaction data separately which could be "uploaded" by some node. This drive could be passed around to several computers which are "off the network" and perhaps even swap longer chains that come in from time to time if older data happens to be on a thumbdrive.
In terms of where to send the data, it would be essentially irrelevant as long as you are not double spending the same coins and that eventually the data gets incorporated into the main "internet" nodes. Confirmation would obviously be substantially delayed.
This thread went over some of these somewhat related concepts and is worth reading:
http://bt.irlbtc.com/view/506.0The issue here really is one of what happens when you have isolated networks that occasionally have communication with each other with latency on the order of tens of minutes, hours, or even days. In the case of a sneakernet that latency is on the order of weeks or even months potentially.
Unfortunately this other thread digressed into silliness, but it really is a variation of the same theme.
