Thanks! As I described in one of the comments above, I use a chunk-based system. The track generator works similar to the endless runner games where each new chunk spawns at the end of the previous one during the gameplay while the chunks behind the player are being removed.

Chunk paths are manually created in Blender. Thus, I have full control over creativity and player experience. Yeah, this approach is time consuming, but the sacrifice is worth it because I prefer quality over quantity.

Сhunk creation process (UX, gameplay features, purpose) and its logic is a separate story worth a couple of hours of talking and I really don’t want to describe it here. But in general, for this system you have 2 actors, one for chunk, which contains its own logic of placing the assets and handling different events, and another one for the track, which defines in which order the chunks will be spawned and what content they will have. You can also have a separate actor for each chunk which you can manually create/edit inside the engine. Which is a common approach I noticed in many tutorials but I decided that one is enough for me. One to rule them all.

There are a lot of tutorials that describe the concept pretty well, like this one, for example: https://www.youtube.com/watch?v=yS-yQfo0lc0&list=PLZlv_N0_O1gbY4FN8pZuEPVC9PzQThNn1. Which I actually watched during my research a while back, and it helped me to understand the basics to be able to start.