Yes, we would save successful settings and maps and have them ready for future runs. One idea is to go through a General War-style history in roughly chronological order, and then restart at the beginning once it has played out, taking any lessons learned into account.
One of the keys to a ToW model would be to make sure map changes during one run affect the next mini map. We had been planning to have one master map (which Stumpy has already designed), and then keep track of the map changes on our master so each new chapter would have a map based on the latest territorial shifts and relative strengths. If SQL were enabled for OP, we could also start to get into a true OOB with ship assignments, prestige or ship carryover between games, on-the-fly map adjustments, etc.
Even done in small parts, this is a big project, which is why I bring it up as an idea for cooperation among admin groups.
On the Andros (and Tholians, and WYN), SFCX had worked on them last year, but we probably need to revisit them for a fresh look. We would need custom shiplists depending on what races are used. If I ever finish it, we would use a single SFB-based shiplist as a master list that corrects default shiplist errors and adds many ships (though probably not as many as FireSoul's list). The SFB list would be designed specifically for D2 play, though it would be good for GSA play -- just not optimized for it.
However, until we can get such a thing off the ground, we need more good campaigns on OP to rebuild the population.