@Volans pinged me on dbstore1002 has stuck replication on x1 and s4 after new database creation. After I was able to check it x1 was already catched up but s4 just lagged.
After trying out several ways to fix it I thought the disk system performs bad (the host has spinning drives, and it's RAID is degraded T206965) I was thinking maybe stopping all other slaves will make the table creations able to finish.
I stopped all slaves, restarted s4, and the tables were created.
I restarted all the slaves, and all were catched up (s4 is still in progress as it gathered more than 10000 seconds of lag)
However I am still not sure why the empty table creations were not able to finish.
I'll take a look in this later.