I agree with your opinion that protecting shitty maps is dumb, but, when it comes up to professional entity work, I choose that kind of protection.
I’m mapper myself, and I make provate maps for my clan, and I espicially asked our clanreader to make something that wouldn’t allow players to have whole map by just downloading it off a server. I asked for that because I make things that use very tricky parts of source engine and I don’t want to see that stolen and used in every shitty map made by some vmex-crazy newbie. That happened to me more times than once and I want to prevent further entitywork theft.
If you still think that no trick is worth such kind of protection, I’ll give you short list of things like that:
-Proper prop_physics unparenting that saves physical properties
-New kind of effects(Exploiting functions leftovers has never been so fun!)
-Alot of uncommon and unknown entity settings
Sorry for not telling exact examples, I want these to be my know-how. You can call me an ass, but hey, I discovered these, I decide what I do with these.
So basically that protection is needed when you don’t want other servers to take your map or when you don’t want newbies to steal your piece of work that took you hell lot of time and effort.