I agree, the core of the module should allow for flexibility - but I am also unsure as to whether or not it should just be left at hooks for future modules.

For instance, I would like to keep a lot of the flexibility I have already coded, and not have to write an additional module (or split the two apart) to provide the anti-leeching mechanism. I think perhaps brainstorming all of the different "core" features, such as time limit, allowable clicks, allowable IP addresses, etc., is fairly broad enough to be usable by everyone requiring downloadable content - enough so, I think, to have them as selectable options in the File Product core.