Basically, the Hyperloop is just a different Maglev. Of which there are already severel with completely different approaches and visuals, so that including them would already require multiple different track types. So before "hyperloop_track" is viable, you'd need "transrapid_track", "jr_maglev_track", "berlin_m_track" and so on. Oh, and let's not forget broad gauge. Or rather, that there are 20 different named gauges.
Since all of those would be copys of each other with different names, I once proposed on the German forum to change them to a more modular approach, allowing the pak creator to invent a new type of track just by defining it as 'something'_track. So you'd remove things like monorail_track or maglev_track from the code and have it work for all x_track.
While this was turned down as impossible (I don't understand code, so there you go) it was also said by prissi that more track types are not needed at all, since the track types we have are not used sufficiently currently.
I think that's wrong, since something like the Hyperloop is complete just with one track, signals, and one vehicle if it's supposed to deliver only pax, more (which would look almost identical) for mail and goods. But why would one do it if it can't even be in a set?
Edit: What I proposed back then, after a while of tinkering around, translated:
I'd like to write [xxx]_track as the waytype in a dat file, where [xxx] is any word - I want to do this with ways, vehicles, signals, depots, stations... . The game should realize it's a track, a track of type [xxx]. The game knows how to handle a track. [xxx] only makes sure that only [xxx] vehicles bought in the [xxx] depot move on [xxx] tracks, and [xxx] tracks don't connect to any other tracks.