Any chance we could get an option to change how much energy the Atomic Disassembler uses?
I found this in the Config under "General":

I:DisassemblerEnergyUsage="x"

Changing this doesn't seem to have any effect on the Atomic Disassembler... so I'm guessing either this setting is meant for something else or simply isn't working as intended. Either way, I'd like to have a way to either scale all the amounts (eg. increase or decrease overall Disassembler power usage), or assign individual usage amounts to each mode on the assembler.

The DisassemblerEnergyUsage seems working for me. Changing its value from 10 to 1000 definitely increased the energy usage.
Breaking a block costs 10 energy by default, 1000 after my change.

Could you provide a scenario where it isn't increasing as you think it should?

Changing the value for me has no effect, screenshot below after the change from default to 1000:

Note: I used the assembler on some dirt to make sure that the problem wasn't simply with the "Efficiency" stat on the tool-tip (which I understand is supposed to display the energy usage), the result was that 20 J were used for each dirt mined, which is the same as if I had not changed the config at all.

pastebin of my config file:
https://pastebin.com/NX38ifWj

Seems like for some reason the setting simply isn't working for me.

Tested on a fresh install:
Forge: 14.23.1.2566
Mekanism: 9.4.2.327
(+ some thermal expansion mods.)
Same results.

Wierd... I've tried again, same result as my previous test.

Fresh install
Forge 14.23.0.2545
Mekanism latest dev

Test method:
Make sure "DisassemblerEnergyUsage" is 10 in the config
Launch a game
Give myself 2 atomic disassemblers
With 1, dig 10 dirt blocks (default left click)
See remaining energy value is 998.0 kJ
Shutdown game
Edit config "DisassemblerEnergyUsage" to 1000
Launch game
With other atomic disassembler dig 10 dirt blocks
See remaining energy value is 800 kJ

@AcidKat, looked though some stuff, I can't find an explanation to the stuff your seeing.

Is it still happening?

Problem persists, unchanged from the behaviour I stated before, (even after update to forge 14.23.1.2582 & mekanism 9.4.3.330)