I appreciate your concern and totally agree with you, Codeforces schedule is in fact the first important thing I consult before scheduling our own contests. I really wish I could help it, seeing all the supports to your comment. But there were sadly a few uncomfortable drawbacks to face if we rescheduled our contest:

• Back when the MathMash round was being scheduled, I checked all the major coding platforms, but today's CF round wasn't listed back then. And I've also recently not been able to stay much regular at CF. As a result, the first time I noticed today's CF round had been during writing this blog, with less than a day to go. And I didn't feel confident enough, that after a week of being scheduled and sending out emails, we can suddenly inform all the members of this abrupt change. It'll be a far more sad incident, if even a single participant came to join the contest after anticipating it for a week and missing in the end just because we suddenly decided to move it forward.
• A few of the most relied upon setters will be participating in the upcoming IMO and so they're not avaliable most of the time at the moment. They have to finish up preparing their assigned problems during the last day to the contest. So, suddenly rescheduling the contest forward, will also make it risky to set up everything properly in the server before the contest, shortening the already little time we get before the round starts.

I hope you'll understand the issues. It's been a busy week for me, but I wish I had seen the CF round coming yesterday. However, I'll try to watch out more often from now on so that these scheduling issues could be avoided in future.