These are the results for 'cheapest month' and 'everywhere' from DC
https://www.skyscanner.com/transport/flights-from/wasa/?adul...
I'd assume it's two reasons: first that it's hard to get the UX right. There are going to wind up being so many combinations of possibilities that I'm not sure how you'd even sort them in a meaningful way. (E.g. it's unlikely price from lowest to highest will be the most meaningful, the lowest price alone might wind up having 100 different date combinations, so figuring out how to present the options in a meaningful way might just be something we haven't figured out yet.)
But second, it might just be too computationally expensive. You see how slow sites already are just for searching a single date, because there are so many possible combinations of connections to consider, and so many fare rules to calculate prices out of. Now a 2-week range for both start and end results in taking almost 200 times longer. It just might not be feasible, or worth the programming effort. I remember a blog post a long time ago from Kayak (I think?) talking about the insane effort that was required to cache flight fares just so show simple fare comparisons across a few days... and it only worked for the flights that were more commonly searched for.
I think the computational cost is a far bigger problem for these kinds of services than the UX.
It was sort of hidden for a while because we were testing other features, but it's back on the main search screen now.
Disclaimer: I work for Hopper
Edit: Forgot to mention this feature is only available on iOS at the moment...
We are building our search engine (focus on EU low-cost mainly) which allow what you looking for (even if you want to search this) for example: A -> B [stay 2-6] -> C [stay 10-12] -> A
Even services that "allegedly" advertise they have that, still require manually clicking every day combination.
I'd fly more often if it was easy. The few times I tried, it would be just faster to drive than go through all possible 900+ day combinations.