Short answer is no. But the longer answer you may find of interest.
Note that embedded metadata in this context refers to the usual song data like artist, title, album, cover art, and so forth. It is normally stored inside of each song file.
The Helios DSP metadata on the other hand is different and is not embedded inside of each song file, but exists separately within your Helios database. This latter metadata describes how each song actually sounded.
It’s always great if your files already contain embedded metadata, such as ID3 for MP3s or the much better Vorbis comments tags for FLAC and Ogg/Vorbis. However, many businesses do not do this and instead prefer to store their catalogues assets in WAV master files and identify each song by a unique hash or other identifier meaningful internally to their organization.
The WAV format is derived from the RIFF container format which was designed in 1991. It did not anticipate contemporary requirements, such as the need for metadata like artist, title, album, cover art, and so forth.
Nevertheless, the way WAV format is generally used today, it still has some benefits. It is not compressed which makes it fast to load. It is a simple format that is easy to work with from a software development standpoint. It therefore remains in widespread use for storing high quality studio masters.
But this can be done without sacrificing any audio quality, preserving the original audio data bit for bit, and using only about half the disk space on average. Consider migrating your catalogue to FLAC.
If Helios detects embedded metadata in your files, whatever format that they are in, it will extract and store that data. Although convenient, embedded metadata is notessential and should not normally have any impact on how songs are analyzed.