What are the performance hiccups when building plugins?

lets say we’re registering 3 post types: is it worse for performance to do this in 3 different plugins (one for each post type), than registering all 3 in one plugin? in other words, is using an extra plugin adding to the load time, even if it doesn’t do anything?

The technical process of plugin load is a simple PHP include. So there is no significant penalty to have more plugins loading than less, however it’s not quite simple as to say there is no difference.

if I use wordpress’ functions to look up the value for 2 different options, is that then considered 2 mySQL queries?

In a nutshell WP options can be set to autoload or not to individually. All autoloaded options are queried once per page load with single query. All not autoloaded options will require additional query per option.

What parts of a plugin is likely to cause additional load times to normal non-logged in users loading the theme?

Plugins contain arbitrary code and in turn cause arbitrary performance issues.

What are the most important do’s and don’ts when it comes to performance in plugin development

Do not guess, do performance profiling.

How does language translation with get text influence performance?

While translation is not especially slow, it can quickly add up when dealing with hundreds and thousands of calls. It is kind of necessary evil from performance point of view, but always keep an eye out that you are not doing too much wasted movements with it, like translating same strings repeatedly.