I think can't find component is misleading error message and simply hide the real error.
I suggest to build a new and an empty project and start to add these component (you listed in
DFM) one by one, BUT do the following:
1) try add them at design time, might be caught the culprit.
2) Create them at runtime and get the real
exception, the one that TReader had eat.
In case that fail too, or may be as different approach, use DDetours
https://github.com/MahdiSafsafi/DDetours on that offending TReader.FindComponentClass and capture the missing/failed class to register at runtime, because this is what is happening, some class/component should have registered itself at runtime in initialize clause (in a
unit) but failed and didn't register, this left the
DFM reader/builder/creator in the dark.