I like to tag each track using the original release year. Then (for example) in best-of albums each track still shows the correct year instead of the year the compilation has been released.
Unfortunately, MusicBee does not like this very much.
It's true that when you start doing "interesting" things with common tags like
Year or
Artist you can confuse MusicBee pretty quickly.
Thankfully, with a bit of practice you can create views with virtual tags to achieve some good results.
(Noting that doing so may affect the user experience in other music players or apps)
Here I've got a compilation album that shows the date it was released:

But each track also knows which album it appeared on and when it was originally released:

This relies on a custom
Media Type tag, so in views showing compilation albums it will show the album date instead of the track date.
Perhaps you can consider using the correct year tag for the album as released, but then use the ORIGYEAR field to indicate all of the individual track release dates?
The reason I decided against doing it this way (which is sort of the reverse of what I
am doing) is that MusicBee won't use that original year value in searches, or the Column Browser, or the Jump Bar etc..
So in my example, if I select 1970s as the decade in the Column Browser,
The Jean Genie won't be included in the results because MusicBee considers it be a 2005 release.
Besides that, I just think it's kinda neat to be able to see the original album information for compilation tracks, singles, soundtracks etc.
Historical side noteThe
Original Year tag in the now ancient ID3 specs was intended for covers of previous material, so I don't think it would be desirable to have it included in search results etc. because it wouldn't match the intended usage.
The 'Original release year' frame is intended for the year when the
original recording, if for example the music in the file should be a
cover of a previously released song, was released.