AFAICT, as of commit a0a422c,  we have 2 different logics to evict outbound peers : lagging-chain (`ConsiderEviction`) and (`CheckForStaleTipAndEvictPeers`). The former to sanitize out lazy/buggy peers who have never sent us a valid header and are always staying behind our tip, the latter triggered in case of stale tip due to block variance to seek a better chain by rotating our outbound peers if we already reach an outbound limit (`EvictExtraOutboundPeers`).

Block-relay-only peers were introduced by #15719. Contrary to outbound full-relay peers who provided us at least a useful header, they're not protected by lagging-chain eviction.

We actually have a comment inside `ProcessHeadersMessage` indicating the contrary behavior. We should either document cleanly that block-relay-only aren't protected or effectively extend the scope of protection to them.

Hinted during #19724 review, see https://github.com/bitcoin/bitcoin/pull/19724#discussion_r475144532
}
        }
        return;
    }
    
    LogPrint(BCLog::NET, "Unknown command \"%s\" from peer=%d\n", SanitizeString(msg_type), pfrom.GetId());
    return;
}
bool PeerManager::MaybeDiscourageAndDisconnect(CNode& pnode)
{
    const NodeId peer_id{pnode.GetId()};
    PeerRef peer = GetPeerRef(peer_id);
    if (peer == nullptr) return false;
    {
        LOCK(peer->m_misbehavior_mutex);
        
        if (!peer->m_should_discourage) return false;
        peer->m_should_discourage = false;
    } 
    if (pnode.HasPermission(PF_NOBAN)) {
        
        LogPrintf("Warning: not punishing noban peer %d!\n", peer_id);
        return false;
    }
    if (pnode.IsManualConn()) {
        
        LogPrintf("Warning: not punishing manually connected peer %d!\n", peer_id);
        return false;
    }
    if (pnode.addr.IsLocal()) {