Did this years ago and learned a ton, that said I'd probably never do it again. Once you know, you know. And sometimes you wish you knew less.
If you don't do it reflectively, and simply copy and paste command lines, then I agree, you're not going to get anything out of it.
As it was, I had to debug a few build issues here and there, with version drift; that too was educational.
The biggest thing to come out of it for me, apart from understanding the Linux boot process better and a greater appreciation for chroot, was getting comfortable with ./configure [options] && make && make install for installing software from source.
Is my understanding correct that these are the things that you definitely have to work through with LFS?
As for bootstrapping, it's been a while since I did it, but that was mostly just setting up grub and pointing it at your newly minted kernel. Grub handles all the "where is this on the disk" issues for you.
This is how I felt when learning Go, coming from a background of OOP languages. But it was worth it.
Parent has answered the first part of your question. As for why Go was worth the trouble, is because of its Utility nature, it has been the perfect replacement for Python as it doesn't have performance limitations(no need to find C extensions) and I'm rolling out production applications faster than ever before with Go.