Next ores are Nether Variation of usual ores:

oreNetherCoal
oreNetherIron
oreNetherGold
oreNetherDiamond
oreNetherRedstone
oreNetherLapis
oreNetherDiamond
oreNetherEmerald

They should be acceptable by ore processing machinery and give twice as usual processed output.
E.g. Nether iron Ore -> 4 Iron dust or 8 iron shards
Mod that adds Nether Ores: https://mods.curse.com/mc-mods/minecraft/241576-nether-core
Other mods (example: EnderIO) already supports that ores

Not my mod. I don't even making minecraft mods @ThatGamerBlue
Before 1.10.2 there was another mod: Nether Ores by Team CoFH
I put mod name for easier debug on developing Nether Ores support

Because in GMod, when someone reports me a conflict/bug of my addon with another addon, or just to make my addon compatible with another addon, they says mod name and link to it and it's fine for me. I don't know why this is bad for you.

Why are you here advertising your mod? Get out.

Supporting every novelty ore out there isn't feasible. There are solutions out there for adding support, such as Unidict or Minetweaker for example. It's up to the modpack makers IMO to add compatibility if they want it. If every mod author hardcodes support for 200 different ores then that author has to constantly update support and balance around said ores. That isn't fair to mod authors, and that's why there are tools for modpack makers and players alike to tweak their instances as they see fit.

In balancing, Nether ores was never changed, they always give twice output. EnderIO, IC2, ExtraUtils and many other mods supports nether ores, why can't Mekanism?

I don't understand why they can't use the default ore dictionary terms for their resources, the addition of 'Nether' seems a bit silly. I'm normally fine with adding extra integration but this doesn't seem logical.

@aidancbrady they add nether to ore dictionary prefix because nether ores gives twice as usual output

oreIron -> 2 iron dusts
oreNetherIron -> 4 iron dusts