IMO, brewhouse efficiency is what matters for recipe formulation. "x pounds of grain = y gravity points in fermenter." The rest is just diagnostics & troubleshooting.
Not meaning to resurrect an old thread, but that statement, other than it being you opinion, is completely wrong- especially for sharing recipes, but also for building your own recipes.
Effeciency 'to the fermenter' means nothing, except to an accountant wanting to know cost per beer. The numbers that are important for recipe formulation are 'in the kettle efficiency', and 'in the kettle volume'. Including lauter volume losses would be even better. From there, you can estimate an 'in the fermenter volume' based on projected kettle-fermenter transfer losses (trub, hops, deadspace, etc.).
Using 'to the fermenter' as 'Brewhouse efficiency' specifically prevents scaling a recipe and adjusting 'trub loss' for the new recipe size/ingredients, at least not without iteratively increasing/decreasing 'in the fermenter' efficiency and resultant effects to other variable in order to home in on the correct 'in the fermenter' efficiency.
Setting 'trub/chiller loss' to ZERO, is the easiest method for using BeerSmith, which effectively changes 'brewhouse eff' to 'in the kettle' or 'lauter' eff. If you want, you can use 'fermenter loss' as a place to log 'trub loss' without BeerSmith using it to mess up your numbers.
By the way, if you are using BIAB, BeerSmith doesn't calc correctly for that, or for batch sparging. There is an Aussie spreadsheet that you can use once you have the recipe close, that will tell you what you how to adjust for BIAB. As long as you don't have to scale the grain bill by more than a few percent, you can call it good. If not, you need to scale it in BeerSmith, then go back to the spreadsheet. The only times the re-scaling in BeerSmith is really needed is when the recipe has heavily colored grains.
It shouldn't be too long before there is a brewing SW package that does BIAB/batch sparge correctly. The hard work has been done in the spreadsheet, it just needs to be incorporated into the logic.