It would take some time, and years to get it all (they are massive, especially when you get to obscure targets and non unixy operating systems), but it would not be that difficult from a know-how perspective.
Most of the problems they solve are well understood. They are terrific tools, and very mature, so getting the long tail of features right might take some time.
But overall, not that hard for many people.
For example, LLVM has alternates that aren’t quite drop in compatible, but are close.
In this situation, there are plenty of C programmers out there, so most developers don't need to know anything about these tools.
What that means is that you are not in full control of your entire stack...do you have an idea how to reimplement, improve, or even just fix your keyboard's controller? Your link to the internet, from the way "call before drilling" protection is laid, to HTTP 2? The way your food is trustworthy; heck, the way your food even exists?
Indeed: nobody is in full control in their own life. Scary. Yet also powerful.
I also understand very well that I would have a very hard time feeding me and my family alone. But I knew where to start.
If we apply this metaphor to binutils, how many developers even know what ELF or DWARF stand for and how they would have to use them? How many know what an assembler and linker do and how one would approach to get one if needed?
(Also, why stop at assembly - a macrolanguage, even though it strongly corresponds to a specific architecture?)