Steve and I are telling you the same thing. Model as if millimeters are meters. Leave the model units set to meters. When you export the .stl you shouldn’t need to scale the model in the slicer if the slicer is expecting millimeters. .stl files have no units so what is a meter in your SketchUp model is read as a millimeter in the slicer.
Here’s a little bevel gear I modeled in SketchUp with units set to meters.

All I did was export the .stl file, open it in the slicer, make it do its thing and save the gcode file which I then printed and it came out like this:

The name Layers was changed to Tags a few years after SketchUp 2017.
Yes. That’s what Layers are for in SketchUp 2017. But you should only assign layers to groups and components. Do not assign layers to edges or faces. And leave Layer 0 active at all times.
Yes. It’s probably easiest to think of giving layers to entities instead of putting things on layers.. If Layer 0 is left active at all times, the edges and faces you create will have Layer 0 assigned to them. After you’ve created the geometry for a part, make a component or group and then assign a layer to that component or group.
That actually sounds like you’re doing that correctly. Every LEGO part should be a component so its geometry can’t merge with the geometry of other parts. You can select a set of components and collect them into a component or group as a sub-assembly. These are known as nest components or nested groups. This is useful when you need a bunch of sub-assemblies. Just don’t go crazy with the nesting. It can make editing your model more difficult. Be thoughtful about how you do that.
There are probably a number of threads on that topic. Basically when you make either a group or component you are putting the selection into a container. Think of jars and bottles on a shelf. They prevent the contents from mixing/merging. So you can have the mustard and strawberry jam next to each other without creating a mess.
Groups are basic containers that provide the separation. Components are like groups on steroids with a lot of capabilities that groups don’t have. when you create a group you are prompted to give it a name which is useful when you need to look at a list as in Outliner or create some sort of report. (You could use a CutList extension to give you the counts of all the parts, for example.) If you have multiple instances of a group and need to edit them you have to either edit each of them or go through a bunch gymnastics to replace groups. If they were compoents, editing one edits all other instances the same way so you only need to touch one of them. You can break that relationship if needed with Make Unique in the Context menu.
Components can also be saved into collections so you can use them in future models by dragging instances in from the Components panel. Here I have a collection of hinge components.
If I need a hinge for a project I always check first to see if I’ve already got one or have one that is close and can easily be modified. When I need a hinge I don’t already have I model it for my project and save a copy of it into my Hinges collection for later use. No ppoint in modeling the same parts every time I need them.
Some people get their knickers in a twist when I say this but I only use components even for nesting. I prefer the consistency and having the options that components provide. This works for me but you can do what you find works for you.
By the way, here I’ve put a controlled amount a twist in the track. As you can see there is an inside path and an outside path. I drew the paths with Curve Maker and use Extruded Edges by Rails from TIG’s Extrusion Tools (Sketchucation) to create the surfaces.