Hmm it looks like this in my falloutnv with generated LOD
http://i.imgur.com/N11noXo.jpg
http://i.imgur.com/FbHKr4O.jpg
Other spots look fine too.
The only reason that comes to my mind is those references are altered by some mods in your game. FNVLODGen doesn't build LOD for references that are
1) deleted
2) initially disabled
3) parent enabled (have XESP subrecord)
Get their FormIDs and check in FNVEdit what touches them. Maybe you have some "Goodsprings restoration mod" that progressively switches buildings using parent enable state. Would like to see test results for that spots from others.
The other possible reason is that FNVLODGen can't locate _lod.nif meshes for them, you will need to check that yourself like I mentioned earlier (Ctrl+F3 assets browser is FNVEdit helps a lot). Can't do anything myself here as it works fine for me on vanilla New Vegas installation. We had reports from TES5LODGen users under MO, try to switch off BSA management there if you use MO.
@Gallathorn
Probably there is just no rubble lod mesh provided, must be created by someone first. I don't know the current state of fallout modding community and availability of modders who can create LOD overhaul including remade vanilla lod meshes, new lod meshes and higher resolution LOD textures. The LOD in Fallouts can look as good as in Skyrim (if it could be called good) since they use almost exactly the same LOD system, we just need new lod models and textures. For example LOD mountains in Skyrim use 1024 texture, in New Vegas it is 256, 4x times worse. FNVLODGen unlocks the true game engine potential, but it can't make LOD look better itself.