First of all, as a user of DF for many years and you guys have really hit an absolute HOME RUN with the new monitor fading functionality! For me, it is second only to the addition of the scripted functions/triggers.
Since you've already accomplished the hardest part the good news is you are a stone's throw away from being able to offer your DF users the ability to replace yet another 3rd party utility such as the long running "f.lux" with a couple additions/modifications which I'll throw out as enhancement requests here.
First phase:
Scheduled monitor fading. Add the ability to simply set a schedule with DF GUI (possibly just hook into windows sched tasks on back end) and corresponding back-end DF command-line switch to allow manual task sched for example (enable fading monitor #1 at 9pm and off at 5am in a dark room).
Second phase:
Triggered and scripted function monitor fading. Just as it sounds - add the ability to enable/disable and set all monitor fading parameters within triggers and scripted macros/functions.
Third phase (a.k.a. F.lux killer):
Monitor coloring. Implement the functionality (example open source flux replacement redshift has been around for years with windows guis available too) to apply the "f.lux" style color variances based on moving time ranges/location sunrise/sunset etc. With phase 1 and 2 above complete, tying these features into the ability to then also go above and beyond what flux and others do, and also use the coloring via DF triggers/macros tied to every windows event already available would blow away the competition! (ie. After my 2nd monitor wakes up from sleep, DF automatically re-arranges my icons, changes my wallpaper, oh and by the way, now also applies flux coloring based on the time....but wait.....only if after checking that my app#1 isn't running if is it, then perform full monitor fading instead)......let's see flux do that!