You are right. My response is a statement that settings must be applied manually (something you already know, but I thought it will be reasonable to confirm for anyone concerned).
After a discussion with our development team, the main concern regarding the Standalone Designer is that external assemblies should be distributed along with the designer. Also external assemblies may depend on other assemblies, and all of them must be copied relatively to the tool's exe. If these additional assemblies depend on Telerik Reporting or other product used by the Standalone Designer, there will be required binding redirects.
Having into account the the required settings, it is recommended the settings to be applied by a power user having a knowledge of the content of the external assembly.
The above lines only describe our concerns for not having such feature. We understand the need for having easier access to configuration settings of Report Designers, and we will appreciate it if you log a feature request describing the use case and the expected result (to what extend the UI should cover the customization of the Standalone Report Designer e.g. write only settings or handle assemblies as well).
Thank you for your cooperation :)
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items