Thanks @ChaimSchwartzIroads for providing me with details. I kind of assumed that would be the reason for creating a view...
As I kind of touched base in my previous comment, the reason performance might not be on par with regular/standard polyline feature layer is because in one case linear features are getting generated on the fly (which is computationally expensive); the other case it is all pre-generated. As we know, the rule of thumb is that pre-generated ones always performance better...
... that said, it shouldn't take that long to draw a few dozens of features! BTW, how long it takes for Pro to draw them currently?
Also, how complicated polylines in your roads layer?
That said, in case you haven't done that yet, can you pls do this as a quick test? Export your tabular aka event data in a table (no more views)... this is temporary thing only for the testing purpose... have the route id field indexed. Make sure no joins or anything.
Then create a route event layer off this temp table (not view) where all data are stored. Check if you see any performance improvements.
Next test would be to copy both your table and roads feature class in a FGDB and create a new route event layer off them.
If none of them help, then I'm afraid you need to contact Esri Support... there are a lot of factors that I won't be able to help over this thread 😞 but they can... sorry about that.
Look forward to your findings.