I'm not sure if this would help or not (someone is bound to comment and correct me if I'm wrong) but running the pack through MultiMC might help. You just need to create a 1.7.10 instance and load it once then in settings tick the FTB option in order to sync the launchers. Also increase the permgen size to 256, iirc. Check how much memory it is allocating, too.
I play the pack via LAN with my wife. I host the games and have noticed the same problems with needing to completely restart every so often. The amount of allocated memory being used seems to slowly go up as more new terrain is generated and never comes back down to what was being used prior to the new areas being explored. Incredibly high lag accompanies this as well. With lines like "Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 129040ms behind, skipping 2580 tick(s)" showing up over and over in the console. Normally, we have to stop what we're doing and just let things catch up. This can take up to several minutes. Eventually, once the allocated memory being used reaches a high enough amount my wife begins getting booted from the game and I have to restart in order to continue. On the sessions where we are staying near home doing things other than exploring there are no problems and the allocated memory being used up stays low.
I tried your suggestion MissLid. Thank you for posting it. What I noticed was that the amount of allocated memory being used after first loading up my save is initially higher while using multimc but that after testing things out by generating lots of new terrain the amount of memory didn't budge. I'll have to put it to the test again tomorrow when my wife and I can play together to see if she still gets booted. I did however still get the "can't keep up" messages in the multimc console just as I did when using the ftb launcher as well as the long periods of lag that seem to come with those messages.
Hopefully the cause of this can be nailed down and fixed as it seems to be something causing the pack to be difficult to play for some. This has been one of my favorite packs since discovering it and if there's any further info I can provide to help pinpoint what is causing the issue please let me know. Though keep in mind I may need some good directions if it requires rummaging through files as I'm not too familiar with how these things work from the inside.