Yup, fixed all, thanks for great tips :)

Oh I see, I changed values to fit it better, and didn't know about that overwriting - will fix right away

Since the game rounds values to the third significant figure, if you keep the charge/reload time to 33.3 ms, you won't know whether that is 33.3499 ms or 33.2501 ms.

Game has a refresh rate of 30 Hz. Given enough power, a weapon can do three things simultaneously, at increments of 33.333... ms: load the capacitor, load the next projectile and turn. Loading a projectile faster than the capacitor charge time is useless because your weapon won't actually fire faster (the overall/net reload time that you can see between the info panels on range and turning speed assumes that you don't have enough energy to both load the capacitor and load the next armature, which isn't an issue unless the ship you are mounting it on doesn't have enough energy (capacitor + loader + electric actuators or momentum wheels) to fully service a single weapon).

Signing means giving your module an unique, non-auto-generated name to prevent your module from overwriting user-made modules with same auto-generated name but different size, exit velocity, spread, efficiency, materials used, etc. Usually, people add a prefix in brakets, like [AE], [DCA] or [EFL] (these three are already taken).

Wait, should I be lowering net reload time of 50.1ms or increase loader time only?

Sign? I didn't know it even existed, thanks for reminder, and about reload time - is there specific reason to set it as 33.2ms, like an unity engine limitations?

Matching charge speed to firing rates sounds great, I'll try it right away with given values, thanks!

Here's some tips:
1) sign your module!
2) lower loader power consumption till the reload time on the advanced panel is 33.3 ms (or 33.2 ms to play it safe)
3) increase capacitor power consumption or reduce capacitor total energy till capacitor charge time is 33.3 ms (or 33.2 ms to play it safe)