Leave cron settings as they are, put your conditional branches into the script that is called by cron.
The definition of "interesting packets (ie http, ftp, etc)" on a network is a nice, but not very helpful term. If you are doing a gigabyte download with wget and you open your browser for a Google search, what do you want to happen? Abort wget even if only 2 bytes are missing from the full download, or keep it running even if you only had 2 bytes downloaded so far.
Setting '--limit-rate' for wget will only apply to the next download. Wget will certainly retry downloading later. I don't know if it can resume exiting ones and how reliable that is.
I would rather make the script to look for a certain value in a prefs file to see if a next wget download can begin. The prefs file can be a text file with "run" or "pause" as the content, written by hand or by a webpage script.
Not very sophisticated, but quite simple. That's what I would do.
Linux Archive