Assuming you use Java (I deduced from your previous posts), the best OOP way to do something like this is to attach something of a "Drive" class to the SendableChooser, and have "TankDrive", "ArcadeDrive", etc. classes to represent the different driving techniques. With this you can just have an abstract method like "drive(Joystick)" and call that (based on the SendableChooser or something like that).
Otherwise, you can use a
state machine do the work for you, and have a Smartdashboard (or Preferences - which would be better suited) field called driver type. (We did that last year, worked out fine)