I recommend creating the section in the linker file. It is often easier for the next guy looking at your code to find the section in the linker file.
That is, embedded development follows a path, from writing code to make it work, to making it work reliably, to making it where the next guy can understand 6 months from now.
In that respect most people use command line options in embedded development for changing options, for example code might support two boards and you have a command line option as to which board, or if you build for debug or release. Whereas the linker file would be more for global project options that do not need to change per build/board.
Think of embedded development. It is like driving a car, sure you can make a lane change locking up brakes and skidding to the next lane. However the guy behind you expects you to turn on the turn signals and gracefully make lane changes. It is not always about getting the job done, but doing it where the guy behind you can predict what you have done and why so that everyone is safe and comfortable.
Like driving a car there are numerous ways to get where you are going, often it is how to get there so that others understand and can predict what you are doing and why so they can stay out of your way.
Trampas