Chisels-and-Bits VS architectury-api

Known performance issue

None of the current open issues on the chisel&bits github reflect your problem so it looks like just an issue on your server and not a bug in the version of the mod used.

That looks like unlocalized text. It's supposed to be this line: https://github.com/ChiselsAndBits/Chisels-and-Bits/blob/fa211eff2f82e3eccd5655f57f14912298519ecd/src/main/resources/assets/chiselsandbits/lang/en_us.json#L404

Architectury, an API for Multiplatform mod support. Needed for Identity.

Using Architectury is likely the easiest method

Okay, with that out of the way, here's what I believe to be true: There is no such thing as a one-size-fits-all code "translator" or "bridge" that can translate regular Fabric code into something that runs on Forge, or vice-versa, and something like this isn't possible in the way I think you're imagining it. Forge and Fabric work very differently from one another under the hood. There is no library that allows you to write Fabric code that works on Forge, and there probably never will be. However, there are some projects out there that aim to lessen the impact of this problem. Architectury is one of these projects. Architectury can translate some parts of a mod between the two loaders, but the mod still has to be built around it. You can't just add it to a Fabric mod and expect it to run on Forge (or vice-versa). Instead, the mod has to be created with it in mind all the way through. Mods can not be converted between Forge<->Fabric automatically. Manual porting is possible, and mods can be built to run on both loaders, but it is not possible to make a universally applicable "converter".

It has been in pre-Alpha for over a year. It won't be happening any time soon, and will behave like Architectury, but with significantly more abstraction for the modder, if / when completed.