Currently the bluetooth_tracker integration still needs to be configured in yaml. That means that you do not get all the advantages for easily maintaining and configuring BT devices in the UI.
Also it still uses the ‘old’ known_devices yaml file which has become deprecated already a while for a lot of other device tracker integrations (in my case it is the only integration that still does that). See also this statement about phasing out known_devices.yaml for all device trackers.
As this integration is in the TOP 100 of most used integrations I would expect that it would have been migrated to this new kind of configuration by now.
To me it is not 100% clear if the following architecture decision also applies to this integration but it would be helpful to encourage the integration owner to get this done.
