Redefining the CCM name without using another CCM

Some services I use require instances to have a specific name that starts with ‘gce://’.
I got it to work using --kubelet-arg=provider-id=... without using the --disable-cloud-controller option.
Could this cause internal problems in a K3S cluster?

Many thanks