When you set enabled=false this completely disables the agent, it won't even try to reach Kibana to get configuration, thus you can't re-enable it afterwards.
If what you need is being able to start the agent without capturing any data, but still being able to enable it later on, for example through local properties configuration modification or with configuration in Kibana, then you only need to start it with recording=false at startup.
Running the above CLI command when the agent is already attached but disabled won't allow to make it start.