It currently contains 1 template, which generates DefineField(enum, ... ) overloads in the ResultsetFields class.
If you start a new project, you probably don't want that, as it generates a lot of code, and you can now also do:
ResultsetFields fields = new ResultsetFields(1);
fields.DefineField(CustomerFields.CompanyName, ..);
which use the generic DefineField routine which accepts a field object rather than the enum, so you're not stuck with a gazillion overloads of DefineField.
If you are migrating an old project, it;s of course key to have these overloads as your code is probably using DefineField(fieldindex enum ... ).
The templatebindings list is a priority list. The templateID's which are bound in a templatebindings set which is ABOVE another templatebindings set which binds the same templateID overrules that latter templateID binding. THis way you can overrule the default templateID bindings shipped with llblgen pro with your own bindings to modified templates for example, by simply dropping a new templatebindings file into one the templates folders and you're set.