This is a follow-up on, but not a duplicate of, Programmatically creating a content type with file field in a custom module.
As suggested by Tenken in a comment to the OP of that question, it is easy to do this by using the core FieldUI module to create the fields, and then then use Features to export the fields to a custom "Feature" module.
You can then install the "Feature" module as any other module that implements a custom content type, but you need to have Features installed for it to work.
I want to use the FieldUI and Features to create a custom content type module, but the module should be stand-alone (i.e. not depend on Features for (re)creation of the content type).
Is this doable? Or is Features a dead end in my use-case? I.e.: If I want a stand-alone module, I must create it from scratch.
And if it makes sense to use Features, what do I need to do in order to transform the "Features" module into a stand-alone one?
(I've searched for similar questions, but not found an answer that describes how you make the generated "Features" stand-alone.)