I feel like I might be about to open a can of worms. Apologies in advance. Also, I'm not a bonefide expert in any of this stuff. But, Helix Native inside PluginDoctor reveals some interesting things.
Helix Native running at 44.1kHz sample-rate. With zero processing inside the plugin:
Helix Native running at 48kHz sample-rate. Again, with zero processing inside the plugin:
This shows us that at 44.1kHz sample-rate, even with no processing, Helix Native aliases.
Now at what point does this aliasing kick in? If we use the decibel range selector on the right hand side, we can check:
It seems that around -106.7dB, aliasing starts to kick in. That means signals from -106.7dB to -200dB will experience some form of aliasing. This is regardless of what processing is going on inside the plugin.
Here are the images for 88.2kHz:
And 96kHz:
Conclusion: If you care about this aliasing, do not run Helix Native at anything other than 48kHz sample-rate.
Whether this goes any way to explaining what
@MirrorProfiles is reporting, I couldn't say at this stage. In theory even if humans cannot perceive these sounds directly, it could cause some sort of inter-modulation artifacts, which could be described as squirrels.