Most of the events in that MIB are "status change" events. I am not an SNMP/MIB expert, but these types of conditions are set up to detect changes in hardware status and cannot be controlled the way you want to. In other words, there are "sub" status codes that come from specific conditions. So, you may have some that are informational, warnings, or critical errors all from the same OID/event and you can't change how any of those "sub" states come into SIM or filter them specifically.
So, what I am saying is, no matter what you change your event settings to, it has no effect on any of the "status change" type of events. This is a fairly annoying issue since most of the hard drive and system battery alerts are of this type.
I had to implement a workaround so I would not miss drive array issues that came in as "minor" or "warnings". For example, I wanted to know when a logical drive array went into a "warning" status because very often, that is a failed rebuild or a repeated rebuild event, where there is no physical failure (yet), but there is logical corruption or something showing a failure may occur. Normally, I don't send anything under "major" or "critical" for auto-ticketing. I had to create a separate collection specifically for the Proliant Storage category, then send anything from "minor" on up to make sure I received them all.
I opened a case with HP on this a while ago and was simply told, that without editing the MIB you can't do much about these. Since each SIM update replaces the default MIBs, i decided to work around it the best I could.