Just as one example. A years-long open submission and selection process. In what way do you feel that results in a 'monoculture'? How would it be done differently and better?
I used to work as a contractor for the Dept. of V.A. and am familiar with the red-tape required to implement libraries in code, push patches to production, rely on 3rd-party libraries, etc. It's a nightmare. As an admin, I couldn't certify a hard drive was digitally wiped unless it did the DoD 3-pass, even though I'm confident a single pass of zeros is sufficient. I couldn't use my LUKS encrypted laptop on premesis, because the encryption process hadn't been vetted by a committee. I couldn't deploy bcrypt as the password hash for authentication.
So, my reference to "NIST/NSA monoculture", is the bullheaded requirement that only NIST-approved algorithms can be use, after committees and approval. It's a monoculture, because at least for the V.A., only government standardized algorithms are allowed.
I just don't think "monoculture" is the reason why. I think all crypto standards organizations are problematic.
If you are defining "evil" as blind and bullheaded, then yes. I don't think NIST or the IETF are actively malicious, however.