**Expected behavior**: Disabling DNS seeding (`-dnsseed=0`) should make Bitcoin Core use the fixed seed nodes immediately on startup (assuming an empty `peers.dat`).

**Actual behavior**:  The fixed seed nodes are used but only after an unnecessary 60 second timeout, and a somewhat misleading log message ("Adding fixed seed nodes as DNS doesn't seem to be available.").

**To reproduce**: `rm ~/.bitcoin/peers.dat && src/bitcoind -dnsseed=0` and wait... 💤 

This issue is probably a "good first issue" :)
{
    LOCK(cs_totalBytesSent);
    if (nMaxOutboundLimit == 0)
        return 0s;
    if (nMaxOutboundCycleStartTime.count() == 0)
        return MAX_UPLOAD_TIMEFRAME;
    const std::chrono::seconds cycleEndTime = nMaxOutboundCycleStartTime + MAX_UPLOAD_TIMEFRAME;
    const auto now = GetTime<std::chrono::seconds>();
    return (cycleEndTime < now) ? 0s : cycleEndTime - now;
}
bool CConnman::OutboundTargetReached(bool historicalBlockServingLimit)
{
    LOCK(cs_totalBytesSent);
    if (nMaxOutboundLimit == 0)
        return false;
    if (historicalBlockServingLimit)
    {
        
        const std::chrono::seconds timeLeftInCycle = GetMaxOutboundTimeLeftInCycle();
        const uint64_t buffer = timeLeftInCycle / std::chrono::minutes{10} * MAX_BLOCK_SERIALIZED_SIZE;
        if (buffer >= nMaxOutboundLimit || nMaxOutboundTotalBytesSentInCycle >= nMaxOutboundLimit - buffer)
            return true;
    }
    else if (nMaxOutboundTotalBytesSentInCycle >= nMaxOutboundLimit)
        return true;
    return false;
}
uint64_t CConnman::GetOutboundTargetBytesLeft()