There is a problem with that approach. Many apps have a small caps button or command. If the font includes small caps, they are used. If they don't, the the caps are scaled down. Your users will need to know to ignore the small caps function and change fonts instead.
You can get a VST plugin for your digital audio workstation (like a font editor, but for music) that replicates the sound of vinyl (painstakingly modeled on the vinyl cutting equipment at Abbey Road Studios). The second video on this page for the product features an experienced recording engineer going into great detail about what makes vinyl sound like it does and why people like it.
Within that folder, I have a folder for banners and other images needed by distributors and for my own site. I have a master Adobe Illustrator file that contains all the different sizes needed. I export required images into separate folders for each distributor.
I have another folder that contains specimens and user guides, both the source documents and PDFs for distribution.
I also make a folder for each new version of the font/font family containing the source documents, finished fonts, and anything else related to that version.
There are a few other folders for keeping information or documents relating the the font/font family as a whole.
I have a completely separate folder in which I put copies of the latest version of each font, organized by family and also by package (some distributors require preassembled sets). Whenever I need to send font data to a distributor, it comes from this folder.
I'm not sure if this is the best system, but I've developed it gradually over a couple of decades and it seems to work for me. I continue to tweak it. It was much less organized even ten years ago.