You know shit. The average Windows user has Microsoft Defender enabled and that is enough to detect malicious drivers regardless of the signature . Even those which are signed are subdued to behavioral analysis . Now trust me or do your research : if a really clever malicious actor want to squeeze a threat into your system it won't be through a driver . But the thing is that most of the people here are not "average" Windows user if they ended up here looking for an audio mod. So most probably they actually have a third party antivirus solution that may ( or may not, actually ) be better at detecting threats , specially on modules that compromises network related activity.
Having said so, the people that ask you to disable Driver Signature Enforcement, mainly self sign the drivers so it does not need to happen on your end. And believe me , a self signed driver exported to another computer is a risk for that people and not you. If you knew how driver signing works, you'll know. Additionally , due to the nature of the chain of validation in modern systems, even disabling driver signature only releases on layer of protection. So even if that people is clever enough to make a driver that takes anything from your computer, they'll count on driver signature being enabled.
In the specific driver package you have linked, it happens to be signed with the original certificates . Those are valid but can not pass the chain validation process because a matching certificate is not the only thing you need in order to load it.
So, next time before you are thinking to sarcastically call "expert" a person that takes time of his own life to modify and offer something paid so you can use it without paying a dime, think that twice
