Three groups of five for scheduling. You could either have eight series with 4-2-2 or nine series with 4-2-2+protected.
I think they could do something like the pods someone else mentioned from the Covid year. You have three geographic groups against which you play a regular three-game weekend series. Then you have inter-group pods where three teams play four games each at one site; these weekends would feature one team from each "group". Play three "pod" weekends, every team hosts one pod. This is seven weekends: four 3-game weekends, three 4-game weekends, 24 games total.
How the groups are established (and even changed from year to year) can be a different discussion, but here's an example agnostic of names/geography...
Group A: A1, A2, A3, A4, A5
Group B: B1, B2, B3, B4, B5
Group C: C1, C2, C3, C4, C5
From the perspective of A1...
Home 3-gm Series: A2, A3
Away 3-gm Series: A4, A5
Pod 1 (Host: A): B1, C1
Pod 2 (Host: B): B2, C3
Pod 3 (Host: C): B3, C4
I threw this out without looking comprehensively, but you would avoid putting the same team in a pod twice. I really want to look at this more comprehensively, but don't have the time for probably months.
Nonetheless, Team A1 wouldn't play B4, B5, C2, or C5 in this "throw against the wall" example. But there's still another weekend vacated with only seven weekends occupied from above. So, either look for another non-conference series or fill it with some type of five-team event. The question is do we want more conference games and internal cannibalization with guaranteed losses? Or do we want opportunities to build conference RPI strength with non-conference games?
If the former, this is where you could have a coordinated "warm weather" event over a week or long weekend where teams not assigned to the same group or common pod would get a few more games in to play as many conference opponents as possible. Or just do another "pod" weekend to knock out another two conference foes.