I think he should be mainly throwing it at the VST vendor, as opposed to the protection software, since the main issue in the article comes from the vst vendor protecting the installer but not the actual software (that said, they also show that the protection software is fairly trivial to hook and bypass)
It sounds like you didn't find any issues with either of them, except that the VST vendor chose not to protect the thing you were hoping to crack?