Possible bug: meta_x509 data still remains in confd after creating backup and selecting remove "Unique site data (license, passwords, certificates/keys, endpoints)

I noticed that creating backups in UTM 9 and selecting remove unique site data will still leave traces of meta_x509 certificate data.  We use a base backup image to provision new UTM's for customers.  While this data does not pose a security risk, there is still confidential information such as email addresses, FQDN's, and address information that remains persistent between creating backups and loading them on new UTM's.