Best practice in the absence of Features in hierarchy

[BA]

Hi Everyone.

First time caller, long time listener.

Its clear that the absence of features in the structure of the hierarchy is a common bug bare for everyone.

I am interested in advice as to what the best practice should be, whilst still tracking true epics and true features.

Suggestions are out there to just use the Epic field for the true feature.  I have a project that is 150-200 features.  Its a very large initiative.  I can see this possibly being an issue with so many "epics (features)".

My concerns are - is this going to set us up for pain later?

If we do this, what is the best way to track true Epics?  Considering the Enterprise, Portfolio, and Program epics are already used for other purposes.

Thanks!