i was merely trying to point out one reason why you might not want really long subexposures.
other reasons include:
1 the longer the sub, the more chances for something to go wrong with tracking (wind, mount issues)
2 the longer the sub, the higher the odds of an airplane or a satellite spoiling the sub
3 the longer the sub, the more chance a cloud could ruin your sub.
4 loss of dynamic range (okay, it's the same thing i mentioned before; the stars being the first thing that will saturate)
#2 isn't necessarily a killer since there are methods to exclude outlier pixels from your stack. but if you have 4 hours of integration time with 30 minute subs (8 subs), it might be hard to get rid of that airplane without throwing away the sub. on the other hand if you have 4 hours with 5 minute subs (48 subs) rejecting the right pixels is easier.
basically the back of histogram trick is a convenient rule of thumb for DSLRs. if you really want to know how long your subexposure should be, you need to characterize your camera (what is the read noise?) and characterize your sky brightness (how much skyfog do i have per unit time?). there is actually a script in pixinsight called CalculateSkyLimitedExposure that can help with this. but until you are running, as sander says, you might as well just use the rule of thumb.