The channels are not available in orderer1 since the TLS certificate for the orderer has been replaced with the new certificate. Since the timeshift is still active, the new certificate is in the future and is not valid.
Be sure to back up all certificate directories before proceeding.
There are two options for moving forward at this point.
Option1 - Continue on the current path
The best way would be to restore the Orderer1 TLS directory and restart the orderer. A best practice would be to copy the TLS directory to a temporary location and enroll the new certificate. Then update the application channels with the new certificate. Then replace the TLS directory with the new TLS cert for the orderer and restart.
Repeat the process for orderer2. After the restart of orderer2, you will need to remove the timeshift from all 3 orderers and restart.
Wait for consensus to be achieved between orderer1 and orderer2.
Repeat the process for orderer3.
Option 2 - Reenroll the expired TLS certificates
The orderers will honor certificates based on the same private key.
Restore the Orderer1 TLS directory and restart the orderer. Replace the expired cert on the system channel.
Upgrade the CA to the 1.5.1 or 1.5.2. Add the reenrollignorecertexpiry to the fabric-ca-server-config.yaml and restart the CA.
This will allow expired certficates to be reenrolled.
Be sure to use the reusekey option to reuse the existing private key.
fabric-ca-client reenroll XXXXXXXXXXXX --csr.keyrequest.reusekey
Restart the orderers.