If you need something like profile within one bundle bounds it is signal that something wrong is happening. In pure modular environment you should not need things like that, because service model keeps you customizations hidden. In traditional JEE applications where your WAR is one big assembly you may not have different options.
You have two options here. First - which you don't like to apply - is to drop additional blueprint file in deploy folder or have additional bundle. Second is to use "blueprint-ext" namespace which allows you to load resource from disk location.