The helper tables can save you some space in your database as far as room in your navigation pane goes. Not actual physical space. But they do add a level of complexity to working with your database, which is why I always include them as an option. And I don't show them in beginner lessons or even my expert lessons. Because they can be confusing if you're not using them right. So when in doubt, no problem, stick with individual tables. There's nothing wrong with that. That's how most databases are built, in fact.

I've been using the Helper Tables more and more and find it much easier to work with.  Working with code... you can copy and paste... and just update the ID field.  And you don't have to recreate the helper table and forms each time you start a new database.  

I have some where I added a field that has Conditional Formatting that I incorporate to other forms and reports.  Much easier than starting over each time.

I am a helper table Phile.
As a matter of fact, in some of our more sophisticated systems, I will have several helper files.
So for a particular manufacturer, I will have a general helper file for things like gender, salutation, et cetera.
Then another helper type that deals with their product specifications which may have up to 20 categories.
And finally, a third one to deal with their parts that will also have up to 30 categories.

And the last two helper tables will have more specific columns to do with that particular industry.

I use my helper table for all of my static small datasets, even my helper type data.  I just self joined it.  I don't know how many tables it has saved me.