Table 101 requires the server to return Bad_CertificateRevoked/Bad_CertificateIssuerRevoked if a certificate from the checked chain has been revoked.
Based on the assumption that a revoked certificate would never be part of a trust list, the returned code should be Bad_SecurityChecksFailed.
In contrast to expiration (another change of state of a certificate while it is trusted), a revocation of a certificate is critical.
Revoking a certficate is a way for the issuer to tell that a certificate is no longer trustworthy. There is a good reason for doing this like a leaked private key.
The expiration of a certificate does not imply an immediate risk, so it may also be suppressed by the server.
Someone who has access to the leaked private key of a certificate could probe servers for the error Bad_CertificateRevoked. This gives him at least the information that this certificate is trusted on this server and possibly on other servers on the same network (maybe with outdated revocation lists).
Hiding this information from an attacker was the reason why only the general error Bad_SecurityChecksFailed should be returned to clients with untrusted certificates.

In short:
A revoked certificate should be treated like an untrusted certificate.