The purpose of the events is to model attributes into the events containing information about your highways, so that you can combine multiple event attributes to create segments. You may be used to centerlines segmented between intersections with a bunch of attributes in that table. IF you have attributes like address ranges that represent to-from, and you split a centerline from one segment into two segments, you will then have to attend to all the attributes to make them valid relative to the new segmentation. IF you have events with attributes, you can just edit the event segmentation for each roadway attribute in the event, then combine/union/intersect the events to create segments for all the attributes you need.

The route contains measure coordinates, "M" values in addition to X,Y and maybe Z vertices, and a route ID, the events contain attributes matching the route ID and measures to-from or along (point events) the route. The routes typically don't contain a lot of information other than being a linear reference for the Route ID and measures, and attempts to embed attribute intelligence into the route ID may be used to some degree, but can complicate maintenance if too much intelligence is embedded - it defeats the purpose at some point.

There can be some overhead effort to getting a usable route system created for transportation systems. I would recommend you check with your local state DOT GIS person to see how they handle the LRS, they might have something you could use for a route reference.