I agree. Reading between the lines, I think they are messing with scheduling priorities. That's not always a good idea.
The scheduling algorithm for any O/S is a finely-crafted piece of code that's been refined over the past 70 years, and circumventing it isn't something one should take on lightly. Of course, it has to be generic and won't always know what's most important to YOU. Conversely, though, you don't know what's most important to the O/S, either.
For example, it was once common practice to raise the priority of the DAW to eke out a few more CPU cycles between audio buffer dumps. But that simplistic approach is no longer recommended. A scheduling optimizer can't know, for example, about the primary application's interdependence with external processes that support it.
So yeh, it might make a spreadsheet load faster. But really, are we so impatient that waiting an extra second to display a Word document is going to ruin our day?