Elastic Fleet Server Agent fails on startup

I don't think that blocks anything, it just means there was an unenroll action that was not acknowledged by 1 agent, maybe because it was offline.

Are you getting the same error when you try to enroll fleet server with the new custom policy? Can you paste here the command output?