WorldRender.SpotLightShadowmapEnable 0 --> Ok this one might give you one fps or two, but it was mostly used in BF3 to distinguish better enemies inside buildings.
WorldRender.SpotLightShadowmapResolution 128 --> If res at 256 was crappy, I cant imagine what 128 would do, lol.
RenderDevice.TripleBufferingEnable 0 --> Only useful if you are using Vsync. If not, you are just adding another buffer for no reason, loading the VRAM even more is not advisable, specially if you are running something like 1GB on FHD
RenderDevice.ForceRenderAheadLimit 0 --> This one is a tricky one, depends heavily on the CPU and GPU config you are using. Some people will see advantages running as high as 3, others would have a better experience running it disabled (0). Default is -1 (which means, it's handled by the driver config).
WorldRender.DxDeferredCsPathEnable 0 --> This is a dead command, was useful in BF3 to gain up to 10 fps in exterior scenes. On interior scenes it borked your performance with high zoom scopes (Metro im talking about you)
PostProcess.DynamicAOEnable 0 --> If you disable AO in video settings, this isnt needed.
WorldRender.TransparencyShadowmapsEnable 0 --> Might handle you a FPS or two.
WorldRender.MotionBlurEnable 0 --> If you put 0% blur in video settings this isnt needed.
RenderDevice.Dx11Enable 0 --> Not useful since the game is DX11 native. Only way to run it (at least BF3 did) in DX9, is using a DX9 card.
GameTime.MaxVariableFps 70 -->This caps your FPS, dont use it at 70 if you are running 120hz monitors (anyways I doubt anyone would get steady 120 fps in this beta, lol).
WorldRender.FxaaEnable 0 --> If you set AA post Off in video settings, this isnt needed. I like FXAA injector's better, it was a lot more customizable (hope they dont ban you for using it in BF4)
PerfOverlay.drawfps 1 --> Shows fps.