I think there are many many ways for a program to detect if it was loaded / infected that would not require the use of a system wide mutex -- many would not res

I think there are many many ways for a program to detect if it was loaded / infected that would not require the use of a system wide mutex -- many would not result in increasing the chance of discovery. So I think adding mutex revocation list would result in false sense of security. While it may combat existing malware it would only be a temporary inconvenience. Not to be too harsh, I feel like solutions like this tend to forget that these are computer programs we are talking about. The entire concept of them is to be able to do things within the constraint of the hardware. The notion that mutexes are a construct coded by a programmer one would expect to be able to make their own mutex without the help of the underlying framework/library you are using today.