On 2.1, I"m not sure this is security through obscurity. I can send a malicious individual a link to this paper saying I used these techniques on my binary but

On 2.1, I"m not sure this is security through obscurity. I can send a malicious individual a link to this paper saying I used these techniques on my binary but fuzzing will still be more difficult. Just like encryption takes my message and jumbles it up to "obscure it", this technique is adding slowdowns and false paths to hinder the fuzzer. Knowing my message is encrypted doesn't make it any easier to read, just like knowing my binary has been fuzzification-ified doesn't make it any easier to fuzz. The only thing that would help is giving you the key to my message, or program paths with added complexity to throw off the fuzzer.