Many configuration elements can be exported and imported using Features module.
Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it declares its components (e.g. views, contexts, CCK fields, etc.) in its .info file so that it can be checked, updated, or reverted programmatically.
Problem is that it only accepts modules that exports their configurations with Chaos tools style, so you can't export blocks, but can export boxes, and so on. Wysiwyg has currently ctools commented out from it's requirements, so you will need to see if it can be exported or not, at it's current stage of development.
If configuration is kept in system variables, you could consider using Strongarm:
Strongarm gives site builders a way to override the default variable values that Drupal core and contributed modules ship with. It is not an end user tool, but a developer and site builder tool which provides an API and a limited UI.
As Clive pointed out, there is also Configuration Management module:
For the most part this module provides the same functionality as a subset of the features module.
The main difference is - it packs only configuration, is smaller and easier to handle, and was written explicitly to deal with "the shortcomings of using features module for configuration management". Still, you are moving whole page, so features with their broader goal might be the way. Your choice.
In all other cases you need to figure out how module stores it's configuration and data, and interact directly with database from your installation profile.