The requirement is to provision default.aspx page when site is created and site
provisioning order is the road block.

I would be adding certain List Views to default page. These lists are created
through a single stapled features which includes custom lists as well as
calendar and tasks lists with custom fields. Lists also contains some lookup
columns.

can some one give some hint what would be the best way to add list views in this
scenario.

I believe <View> elements in Module file will not work as they it may not find
referenece to custom lists and customizated calendar and tasks list.

I have wrapped all the functionality in a feature and handled feature activation
asynchronously (Thanks to someone's blog) with enough delay to make sure default
page is provisioned but this is unacceptable by the end users.

I cannot use Execute URL property due to some undisclosed reason.

I was thinking about a hidden web part which checks if the feature provisioning
default.aspx page is activated and activate it if it is not.

Please recommend how could I have programmed it better inorder to meet required
functionality.