In CVS now are some new SEXPs. None of these are tested, of course.

There's no FRED under Linux.
set-object-speed-(x, y or z)Overrides the current object's velocity (Should I rename to set-object-vel-*? hmm...) Note that it instantly changes the ship's speed; so the speed will likely continually decrease if you set it higher than how fast the ship wants to go.
EDIT: This should also theoretically work with waypoints, too...

And if a wing is specified, then all ships in that wing will have the effect applied to them.
Possible uses: Hyperspace effect?
ship-createThis is a SEXP that basically does some error checking on the variables and then calls the internal ship_create function. It lets you create a ship or ships without specifying it in FRED. But I am not sure if you'll actually be able to use other SEXPs on these ships since they won't exist at mission start.
Possible uses: Escape pods. With the any-ship and string arguments, you could autogenerate them for whatever ship classes without having to create each and every one in FRED.
Of course this is a somewhat dangerous SEXP since you may not know exactly how many ships will be made with it in every case in a mission. Use with care.
mission-set-nebulaTakes a true/false argument to determine whether the nebula is enabled or not.
Right now, I think FRED2 will only let you set the poofs if you turn on the nebula initially. However I've overriden that in the parsing code so that the variables will be loaded anywho if they exist.
If you start out in a nebula you will not be able to use the background nebula; and it looks like skyboxes will be replaced in non-HTL mode.
It will take a little more memory since both nebula and normal stuff has to be loaded, but it shouldn't be anything significant.
I haven't tested this beyond making sure that non-nebula and nebula missions seem to still work properly.