Hey @marcinmarcin,
Assuming SQ means Sound Quality rather than square meters.
Looking at the official changelog, the only change between 4.072 and 4.073 is Node.js version pinning with a static package fallback. This is a backend dependency management fix - it does not touch MPD, ALSA, audio drivers, buffering, resampling, or any component in the audio signal path. From a technical standpoint, both versions should produce bit-identical audio output given identical playback settings.
To answer your direct question: No, there is no security reason preventing you from staying on 4.072. The 4.073 release contains no security patches. It is purely a stability fix for package management. You are not exposing yourself to any known vulnerability by remaining on 4.072.
That said, if you genuinely perceive a difference, I would be curious to know your setup details - hardware platform, DAC, output configuration, and playback settings. Without controlled blind A/B testing with matched levels, perceived differences between versions with identical audio paths are difficult to attribute to the software itself. But if something did change in your configuration during the update process (playback options, resampling settings, buffer size), that could explain it.
If you want to stay on 4.072 for now, that is a perfectly valid choice. You can disable automatic updates and remain there until you are satisfied that a future release addresses your concerns.
Kind Regards,