So the update we gave on the tick-rate talked about two things. Firstly that the issue at the time was that there was a 2/7ths second delay. The following update reduced that setting to only a 1/7th second delay to limit the impact of the issue.
The longer form change is to allow our code to see "when" a shot was queued so that it could harness firing data that exists between ticks. This would make the firing rate as correct as is possible because the timings would all be recorded regardless of tick-rate. This second concept requires code-work and is not a simple fix. The expected time is likely in months for the more complete correct.