"Our new hot device has this awesome performance mode but those benchmarks aren't aware for it and it won't be utilized in the device reviews. So let's make sure it's used in these benchmark applications."
If they just flip the switches available to every developer/application it's not necessarily dishonest just tech marketing.
2. Otherwise, if it require the application to be aware to utilize this feature, then why hasn't Samsung announce this "mode" to developer to utilize it yet?
Also, benchmarks are designed to compare apples to apples, so if, as you suggest, the high-performant mode wouldn't be triggered by benchmark use-cases normally, then hard coding the exception is dishonest, as the only explanation is turning your apple into an orange.
When those particular programs are benchmarks and the path is coded specifically to boost performance on a unique set of said benchmarks in contrast to the most common use cases, that's an issue regardless of whether or not you can imagine an outlier real-world scenario that utilizes a code path that tweaks the performance.
You have to bend over backwards to see that as anything other than dishonest.