Thank you for contacting us.
Unfortunately, dynamic content types must have at least one required short text field. This is by design, the field is used as an identifier of the content - when displayed in lists, for URL generation, searching, sorting, filtering etc.
As far as your second question is concerned, it is always the business case that serves as a decision maker and whether one can rely on existing features of the system or develop a custom approach.
My suggestion for you would be to consider your architecture and if possible, use Sitefinity built-in tools to create it - by using the Module Builder for example. We constantly strive to improve it so it better serves business needs. In addition to all of the out-of-the-box functionality, you could also benefit from existing community discussions, knowledge base articles, documentation and so on.
I hope this information helps. Let me know if I can assist you any further.
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Sitefinity CMS Ideas&Feedback Portal
and vote to affect the priority of the items