Traktor repeatedly displayed the message "WARNING: ID3-Tags could not be read for ..." during startup. Some tracks were also repeatedly analysed, and metadata changes such as BPM, beatgrids and cue points were not always written back reliably. My theory is that a playlist or cleanup tool modified these M4A containers at some point in the past. The affected files played perfectly in Apple Music and showed no obvious corruption.
The relevant log file on macOS is:~/Documents/Native Instruments/Traktor <version>/Logs/Traktor.log
The log contained entries pointing to the affected M4A files.
The root cause was not damaged AAC audio. The issue was the M4A container itself. Apple Music could read the files without problems, while Traktor had difficulties reading and writing metadata.
I rebuilt the M4A containers with a lossless FFmpeg remux using stream copy only. No audio was re-encoded; Apple Music continued to play the files normally; Traktor stopped reporting ID3 errors; and BPM, beatgrids, and cue points remained intact after restarting Traktor.
One additional finding may help others: Traktor escapes certain characters in its log files, including brackets and underscores. If you automatically extract affected file paths from the log, you must remove those escape characters, or some files may be missed.
Hopefully, this helps others who are seeing this error and assume the audio files themselves are damaged. In my case, the audio was fine. The container was the problem.