Simply put, if the default block definitions are in the core library, I expect the toolbox set matching it to also be in the core library, not in the sample projects.
The goal of the sample might change and thus it's selection of tools. Many samples have different selections based on their goal. If the toolbox definition is in core besides the default blocks it gets much more "status" and might get better maintenance or such.
I also think that if both are in core then they can be noted in the documentation as available and when you download the library you get both without going to hunt for the "missing" part in the samples. The way I see it, the default generators and blocks are in core and the toolbox to use them is in samples.... Meaning the library is "incomplete". When googling I found a surprising number of post asking for a toolbox listing with answer al being more and less complete. So I can hardly be the only one that would like a default toolbox included with the blocks and generators.
Maybe I'm overthinking this. But that is how I see it. You did all that work, and one has to find the parts of the result in different places making it easy to miss things you put work in. That's a shame.