I had the same machine and used it for the same thing for two years, was still running Mavericks at that point and worked great. Last winter I updated it to Sierra, 16gb RAM, a fast external SSD and gave it to my daughter's family. They really like it although they have had a couple serious crashes. First time that happened I had to talk my son in law through restoring from time machine. He said he had to do the same thing again later, but since I didn't see it in person I'm not sure if that was really needed.
I now have a 2014 base Mini as an iTunes server and it had El Capitan pre-installed. It has been rock solid so I haven't bothered to update it.
I also have a 2012 2.6ghz quad 16gb mini that I use exclusively for for audio/video editing. Kept it on Mountain Lion for compatability with some very expensive legacy software, but just last week I set it up to dual boot with Sierra on a fast external 1TB Samsung T3 while keeping Mountain Lion on the original Apple internal 256gb SSD.
Have to say, I'm really happy with this machine on Sierra. It runs the new versions of Final Cut Pro X, Logic Pro X and Compressor very smoothly. And the "dark mode" further compliments their user interfaces. I also just upgraded my 2013 i7/8gb/512gb MacBook Air to Sierra and very happy there as well. I didn't find anything compelling in Mavericks, Yosemite or El Capitan so I skipped them all. But Sierra is working out really well for me.
Was surprised that almost all of my legacy software (10 years old typically) still runs on Sierra. Only problem was VectorWorks 2008 and it just crashes. Googling around, it appears to have broken under Mavericks or Yosemite though. Unfortunately it is about a $2500 CAD package, so that's one reason I'm keeping the quad Mini as a dual boot machine. However, I am going to move to AutoCAD LT on Sierra which is considerably less expensive.
The problems with my daughter's 2012 Mini on Sierra are odd. They are not very technical and live over a hundred miles away so I can't really troubleshoot in person. Their first crash was well documented as a bug that affected many people, but I think it was fixed in a later release. They were gun shy afterwards though and I think they still have updates turned off, so that might explain their problem.