No. Nouveau is supported by bumblebee and this would disable this kind of support. Unless you have a good argument against this, I'm going to close this bug report soon.

If nouveau loading is a problem for users, they need to blacklist that module.

No. Bumblebee can work with nouveau even if it is blacklisted. Blacklisting only avoid auto-loading, Bumblebee can load nouveau when needed. ;)

I think I have good arguments:
– This is an official recommendation from upstream (even if this is not clearly stated, we will make it clearer in coming 4.0 — yes, I’m part of upstream). See DEB packaging for instance: https://github.com/Bumblebee-Project/bumblebee-ppa/blob/master/precise/bumblebee/debian/bumblebee.conf
– Since PRIME is enabled by default, if X starts with nouveau loaded, you won’t be able to unload it and use Bumblebee until reboot. That’s a rather big issue.
– Same way, some times Bumblebee is unable to unload nouveau if it’s loaded at boot, which is necessary to him for turning it off with bbswitch and working properly.
– In some cases, if nouveau is loaded before nvidia, this last one can’t work. And for instance, I have both nouveau and nvidia (for testing purposes), with a script to switch easily.
– This has no known downsides (as said above, blacklisting doesn’t make Bumblebee unable to use nouveau — just look at what happens for NVIDIA, it’s currently blacklisted by the aforementioned line, but it does work).

Reverse way, I would say that unless you have a good argument against it, blacklisting is the way to go. ;)

I call that a solid argument. Will blacklist nouveau and push a new package.