For the block page to be shown the gateway needs to intercept the communication and reply with a redirect instruction to the browser.
For HTTPS pages, this can only be done if HTTPS Inspection is enabled, or else the communication is encrypted between the client and the youtube server and the HTTP header can't be modified. In this case, the only thing the gateway can do is send a reset to the client, rejecting the connection and causing the rejection error in the browser.
I don't know why this happens only in your 1400, this should be same behavior in all appliances, unless you have HTTPS Inspection enabled.
Also, remember that connections to youtube might use quic protocol (UDP/443) and this will not be inspected by https inspection. So you might have to block it for the connection to use https instead.