Best Of

Besides all the technical details about baking well-covered above by @Fabi_G (as always !), I think you are going down a weird rabbit hole with this model.

It certainly looks very clean and detailed, but it also looks a lot like something that has been crafted with a CAD-like mindset of trying to put each and every little detail from the reference into the model ... but without many thoughts for the final game use. Which in turn leads you to the somewhat awkward practice of having to bake from and to essentially the same model just to capture hair-thin bevels, while also having to manage dozens and dozens of model parts, and having to pack things over two texture sheets, and yet still having issues capturing some details as seen in this thread.

The effort is admirable but IMHO it is also a bit absurd or even counter-productive as that means that as soon as your textures mip down (or slowly load) you'll end up with a very blurry looking surface - the kind that gamers may refer to as "something out of a PS2 game".

For the sake of comparison here is your car next to a hero boss model from a massive commercial game. Now admittedly MGS3 is about 15 years old by now but the models still hold up beautifully.

The main element of this AAA boss model only weights 12k tris and uses a single (!) 1024*1024 map. But still there is enough resolution to capture all the fine details of the outer shell, and enough UV density and juicy pixels to make the feet details look gorgeous (as highlighted in the bottom-left of the UVs).

Whereas your car weights 86k tris, and uses two sheets that seem to require at least 2048*4096 or even 4096*4096 textures. That means that your indie model of a car is orders of magnitude more resource-intensive than a badass mecha wolf from a massive AAA game.

Here is how the UVs compare. I'm sure you can see that you'll need much, much, MUCH bigger textures than they did just because of the way your model is built.

 

Of course you're probably not going to rework this model from the ground up now that you're that far in. But in the future I would strongly encourage you to look at things more from the angle of what is actually needed for a game, keeping the in-game model and textures in mind right from the start as opposed to spending too much time modeling infinite amount of CAD detail.

It may seem counter-intuitive but good game optimization doesn't happen in the end ; rather it is something that is thought about right from the beginning. For the case of this car for instance you could have taken a few days to build a game model directly at conservative specs, like 20k tris maximum and mostly continuous surface-wise ; then focus on modeling high-poly sources only for the parts that really need them, like the car body, while doing all the minor bevels with simple trim sheets, or by baking a round edge shader, or by simply giving them raw geo bevels. The whole thing would have taken you less than a week including baking and it would have granted you a lot of flexibility to edit/redo parts on the fly.

So going back to your question of "is this how a normal map should look", I would say yes but also not really. There is nothing inherently wrong with it, but outside of a showcase scene with just this one car on screen I have a hard time thinking of a fitting game context for it.

All that said, good luck.