Is it necessary for SQL Monitor to acquire shared locks on objects when monitoring a SQL instance?

We experienced a deadlock on our system when SQL Monitor was trying to query a system table msdb..backupset at the same time that on of our maintenance plans was deleting backup history as one of its sub tasks.

It would be nice if we could either set the isolation level per alert or if you guys would amend your code to use nolock query hints?