Generally if you are flying an industrial of any kind, having a sec status <= -2.0 hurts.
If you jump into a system where you are a “criminal”, you can’t cloak, so even blockade runners, MWD/Cloak trick and any attempt to hide from the NPC police forces is futile.
So in the OP, the criteria I would probably change:
10, all the way to 0.1 – Existing responses in 1.0 through 0.5 sec status space. At 10 you get near immediate concord response, at 0.1 you get the delayed 0.5 response time.
0 to -4.5, you get concord gate guns and whatever’s already on grid assuming you wouldn’t be shot at for having low status already.
-4.6 to -10, no concord assistance of any kind, in addition to them shooting you per normal concord behaviour.
The last criteria doesn’t really help anyone much. The hauling pilot is already going to be engaged by NPCs in every system (once at -5.0 sec status), and freely engageable by players once -5 also, so CONCORD already doesn’t assist for most of that group.
I kind of like the concept. It gives players more opportunity to “antigank” effectively if they could, and any gameplay that puts more opportunity in the hands of players as opposed to NPCs is a good thing in my view.
So if this was implemented, I think I’d rather the criteria be:
5.0 sec status = current response times
5.1 - 10.0 = sliding scale of reduced response time. Those that really grind out to get to a 10.0 sec status gain benefit from that effort, where really it doesn’t provide much benefit currently.
4.9 - -1.9 = sliding scale of reduce CONCORD response time
From -2.0 down, no CONCORD assistance.
And I wouldn’t do the scaling linearly. I’d do it as an s-curve like this (this is just a random image off the internet, not scaled appropriately):